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