Vulnerability in hono (CVE-2026-54290)
Summary
Vulnerability in hono (CVE-2026-54290). Confidential information can be exposed externally. Exploitable via origin. Mitigation: upgrade to 4.12.25 or later.
Original description
The description as published by the source.
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.25, with credentials: true and no explicit origin (the default wildcard), the CORS Middleware reflects the request's Origin and sends Access-Control-Allow-Credentials: true. Any site can then make credentialed cross-origin requests and read the responses, exposing cookie-authenticated endpoints to arbitrary origins. This vulnerability is fixed in 4.12.25.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54290 has been found in hono.
Attackers can target a specific entry point like origin over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade hono to 4.12.25 or later.
If unsure, ask your IT team or search "hono CVE-2026-54290" on the vendor's site.
CVE-2026-54290 (hono) — CWE-942 / CVSS v3 7.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: origin / Origin / null
Patched: 4.12.25 — 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.
A vulnerability (CWE-942) exists in hono. Attackers reach the vulnerable code path via origin without authentication.
Check the vendor advisory for the affected versions of hono. Attack surface: origin / Origin / null.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 4.12.25.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade hono to 4.12.25ステージング環境で 4.12.25 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com