{"answers":{"affected":"3 open source packages ship an affected version, including firefighter-incident.","exploited":"There is no known exploitation of CVE-2026-42864 in the wild and no public exploit code.","fix":"Upgrade firefighter-incident to 0.0.54 or later.","what":"CVE-2026-42864 is a critical server-side request forgery vulnerability in ManoManoTech firefighter-incident, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42864 and fix it if it is affected.\n\nWhat it is: CVE-2026-42864 is a critical server-side request forgery vulnerability in ManoManoTech firefighter-incident, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-42864 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- firefighter-incident (PyPI): affected all versions; fixed in 0.0.54\n- firefighter-incident (PyPI): affected all versions; fixed in 0.0.54\n- firefighter-incident (PyPI): affected all versions; fixed in 0.0.54\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-42864/ (Markdown: https://insights.sbomify.com/CVE-2026-42864/index.md)","id":"CVE-2026-42864","markdown":"https://insights.sbomify.com/CVE-2026-42864/index.md","name":"CVE-2026-42864","record":{"aliases":["GHSA-fqvv-jvhr-g5jc","PYSEC-2026-339"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Incident management application","requires_auth":"none","summary":"Unauthenticated attackers can exploit an SSRF vulnerability in the Jira bot endpoint to steal AWS IAM credentials from the server.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"FireFighter is an incident management application. Prior to 0.0.54, the POST /api/v2/firefighter/raid/jira_bot endpoint (CreateJiraBotView) is reachable without authentication (permission_classes = [permissions.AllowAny]). Its attachments payload is fetched server-side via httpx.get() with no URL validation, then uploaded as an attachment on the Jira ticket that gets created. An unauthenticated caller able to reach the ingress can coerce the pod into fetching arbitrary URLs and exfiltrate the response as a Jira attachment. On EC2/EKS deployments that do not enforce IMDSv2, this allows theft of the temporary AWS credentials attached to the pod's IAM role. The docstring on the view claims a Bearer token is required, but the code does not enforce it. This vulnerability is fixed in 0.0.54.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"FireFighter: Unauthenticated SSRF in Raid jira_bot endpoint allows IAM credential theft","id":"CVE-2026-42864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Inbox Zero: Cross-account cleaner email stream exposure","id":"CVE-2026-42865"},"packages":[{"ecosystem":"PyPI","fixed":["0.0.54"],"introduced":["0"],"last_affected":[],"package":"firefighter-incident","purl":null,"source":"GHSA-fqvv-jvhr-g5jc"},{"ecosystem":"PyPI","fixed":["0.0.54"],"introduced":["0"],"last_affected":[],"package":"firefighter-incident","purl":"pkg:pypi/firefighter-incident","source":"GHSA-fqvv-jvhr-g5jc"},{"ecosystem":"PyPI","fixed":["0.0.54"],"introduced":["0"],"last_affected":[],"package":"firefighter-incident","purl":"pkg:pypi/firefighter-incident","source":"PYSEC-2026-339"}],"prev":{"headline":"Flowise: Mass Assignment in Chatflow Update Endpoint Allows Cross-Workspace AgentFlow Reassignment","id":"CVE-2026-42863"},"products":["firefighter-incident"],"published":"2026-05-11","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["ManoManoTech"]},"summary":"Unauthenticated attackers can exploit an SSRF vulnerability in the Jira bot endpoint to steal AWS IAM credentials from the server.","url":"https://insights.sbomify.com/CVE-2026-42864/"}