← Back
CVE-2026-42864
critical
CVSS 9.9
Vulnerability in firefighter-incident (CVE-2026-42864)
Summary
vulnerability in firefighter-incident (CVE-2026-42864). Confidential information can be exposed externally. Exploitable via `POST /api/v2/firefighter/raid/jira_bot`. Mitigation: upgrade to `0.0.54` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42864** has been found in firefighter-incident.
Attackers can target a specific entry point like `POST /api/v2/firefighter/raid/jira_bot` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.9/10.
What to do: upgrade firefighter-incident to **0.0.54** or later.
If unsure, ask your IT team or search "firefighter-incident CVE-2026-42864" on the vendor's site.
CVE-2026-42864 (firefighter-incident) — CWE-306 / CVSS v3 9.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v2/firefighter/raid/jira_bot / `CreateJiraBotView` / `attachments` / `LandbotIssueRequestSerializer.attachments`
Patched: `0.0.54` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-306) exists in firefighter-incident. Attackers reach the vulnerable code path via `POST /api/v2/firefighter/raid/jira_bot` without authentication.
📍 Affected scope
firefighter-incident — . Attack surface: POST /api/v2/firefighter/raid/jira_bot / `CreateJiraBotView` / `attachments` / `LandbotIssueRequestSerializer.attachments`.
🔥 Severity
Severity: Critical (CVSS 9.9/10). Confidential information can be exposed externally
🔧 How to fix
Update to **0.0.54**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /api/v2/firefighter/raid/jira_bot` requests with malformed payloads or SQL meta-characters. Run `grep -r 'firefighter-incident' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'firefighter-incident' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `firefighter-incident` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/v2/firefighter/raid/jira_bot' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/v2/firefighter/raid/jira_bot` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade firefighter-incident to 0.0.54ステージング環境で 0.0.54 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/v2/firefighter/raid/jira_bot on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
firefighter-incident
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.54"}]}]
PyPI
firefighter-incident
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.54"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42864
- package https://github.com/ManoManoTech/firefighter-incident
- web https://github.com/ManoManoTech/firefighter-incident/security/advisories/GHSA-fqvv-jvhr-g5jc
- web https://github.com/ManoManoTech/firefighter-incident/commit/2586679e6f32c12d223668b73e98f4c4de7b771f
- web https://github.com/advisories/GHSA-fqvv-jvhr-g5jc