{"answers":{"affected":"3 open source packages ship an affected version, including flaskbb.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46556 exists.","fix":"No fix has been published for CVE-2026-46556 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-46556 is a medium-severity server-side request forgery vulnerability in flaskbb, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46556 and fix it if it is affected.\n\nWhat it is: CVE-2026-46556 is a medium-severity server-side request forgery vulnerability in flaskbb, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46556 exists.\n\nAffected packages and fixed versions:\n- flaskbb (PyPI): affected all versions up to 2.2.0; no fix listed\n- flaskbb (PyPI): affected all versions up to 2.2.0; no fix listed\n- flaskbb (PyPI): affected all versions up to 2.2.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46556/ (Markdown: https://insights.sbomify.com/CVE-2026-46556/index.md)","id":"CVE-2026-46556","markdown":"https://insights.sbomify.com/CVE-2026-46556/index.md","name":"CVE-2026-46556","record":{"aliases":["GHSA-xq32-9g7q-7297","PYSEC-2026-2479"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FlaskBB forum software","requires_auth":"low_privilege","summary":"Authenticated users can exploit SSRF in FlaskBB to force server requests to internal endpoints, enabling port scanning and metadata access.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"FlaskBB is a Forum Software written in Python using the micro framework Flask. Prior to version 2.2.1, a Server-Side Request Forgery (SSRF) vulnerability in get_image_info() allows any authenticated user to force the server to send HTTP requests to arbitrary internal endpoints, including cloud metadata services. This is a blind SSRF with confirmed internal port scanning and internal API triggering capabilities. Version 2.2.1 patches the issue.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"FlaskBB: SSRF in get_image_info() via unrestricted avatar URL","id":"CVE-2026-46556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"ImageMagick: Stack overflow in fx operation","id":"CVE-2026-46557"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.2.0"],"package":"flaskbb","purl":null,"source":"GHSA-xq32-9g7q-7297"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.2.0"],"package":"flaskbb","purl":"pkg:pypi/flaskbb","source":"GHSA-xq32-9g7q-7297"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.2.0"],"package":"flaskbb","purl":"pkg:pypi/flaskbb","source":"PYSEC-2026-2479"}],"prev":{"headline":"WhatsApp MCP: Unauthenticated bridge API allows message sending and arbitrary file exfiltration","id":"CVE-2026-46555"},"products":["flaskbb"],"published":"2026-07-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["flaskbb"]},"summary":"Authenticated users can exploit SSRF in FlaskBB to force server requests to internal endpoints, enabling port scanning and metadata access.","url":"https://insights.sbomify.com/CVE-2026-46556/"}