Server-side Request Forgery (SSRF) Affecting firefighter-incident package, versions [,0.0.54)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-PYTHON-FIREFIGHTERINCIDENT-16431740
- published6 May 2026
- disclosed5 May 2026
- creditUnknown
Introduced: 5 May 2026
CVE-2026-42864 (opens in a new tab)How to fix?
Upgrade firefighter-incident to version 0.0.54 or higher.
Overview
firefighter-incident is an Incident Management tool made for Slack using Django
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the CreateJiraBotView class. An attacker can access internal resources and exfiltrate sensitive data by submitting crafted requests to the unauthenticated endpoint, causing the server to fetch arbitrary URLs and upload their contents as attachments.
Note: This is only exploitable if the deployment does not enforce IMDSv2 on EC2/EKS nodes.
Workaround
This vulnerability can be mitigated by restricting ingress access to the affected endpoint to trusted networks, rotating or revoking the Jira API token, or enforcing IMDSv2 with HttpPutResponseHopLimit=1 on EC2/EKS nodes.