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