← Back
CVE-2026-39806
high
CVSS 7.5
Vulnerability in bandit (CVE-2026-39806)
Summary
vulnerability in bandit (CVE-2026-39806). Risk of unauthorized operations or information disclosure. Exploitable via ``rest``. Mitigation: upgrade to `1.11.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-39806** has been found in bandit.
Attackers can target a specific entry point like ``rest`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade bandit to **1.11.1** or later.
If unsure, ask your IT team or search "bandit CVE-2026-39806" on the vendor's site.
CVE-2026-39806 (bandit) — CWE-835 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `rest`
Patched: `1.11.1` — 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-835) exists in bandit. Attackers reach the vulnerable code path via ``rest`` without authentication.
📍 Affected scope
bandit — . Attack surface: `rest`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.11.1**.
🛡️ 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 request patterns matching this CVE's known IOCs. Run `grep -r 'bandit' .` 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 'bandit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `bandit` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade bandit to 1.11.1ステージング環境で 1.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Hex
bandit
[{"type":"SEMVER","events":[{"introduced":"1.6.0"},{"fixed":"1.11.1"}]}]
erlang
bandit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.11.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-39806
- package https://hex.pm/packages/bandit
- package https://github.com/mtrudel/bandit
- web https://cna.erlef.org/cves/CVE-2026-39806.html
- web https://github.com/mtrudel/bandit/commit/ae3520dfdbfab115c638f8c7f6f6b805db34e1ab
- web https://github.com/mtrudel/bandit/security/advisories/GHSA-rf5q-vwxw-gmrf
- web https://osv.dev/vulnerability/EEF-CVE-2026-39806
- web https://github.com/advisories/GHSA-rf5q-vwxw-gmrf