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