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