Quick answers
- Is CVE-2026-46556 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46556 being exploited in the wild.
- How severe is CVE-2026-46556?
- Medium severity, with a CVSS score of 6.5, published 21 July 2026.
- Which products and versions are affected?
- flaskbb (PyPI) <= 2.2.0, ECOSYSTEM:introduced=0,last_affected=2.2.0.
- Is there a fix for CVE-2026-46556?
- A patch was published on 2026-07-21: Version 2.2.1 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46556 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46556?
- Check whether you run flaskbb (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the `get_image_info()` function within `flaskbb/utils/helpers.py`. The application fails to validate the scheme, host, or IP address of URLs provided for user avatars before passing them to the `requests.get()` method. An authenticated attacker can exploit this by submitting a malicious URL (e.g., pointing to 127.0.0.1 or cloud metadata services like 169.254.169.254) via the user settings or admin user-edit pages. This is a blind SSRF that enables internal port scanning through differential error responses and the ability to trigger GET-based internal APIs. The issue is addressed in version 2.2.1 by disabling redirects in the request.
Affected products
- FlaskBB FlaskBB < 2.2.1
Identifiers
- CVE-2026-46556
- GHSA-xq32-9g7q-7297
- PYSEC-2026-2479
Timeline
- 2026-05-19: advisory: GitHub Security Advisory published
- 2026-07-21: disclosed: CVE published to NVD
- 2026-07-21: patched: Version 2.2.1 released