Cross-Site Scripting (XSS) in hono (CVE-2026-56761)
Summary
Cross-site scripting in hono (CVE-2026-56761). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.12.14 or later.
Original description
The description as published by the source.
hono before 4.12.14 contains an html injection vulnerability in jsx server-side rendering that allows attackers to inject unintended html by using malformed attribute names. Attackers can craft specially crafted attribute keys containing characters like quotes or angle brackets to break html tag boundaries and inject arbitrary attributes or elements.
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-56761 has been found in hono.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade hono to 4.12.14 or later.
If unsure, ask your IT team or search "hono CVE-2026-56761" on the vendor's site.
CVE-2026-56761 (hono) — CWE-79 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 4.12.14 — 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.
Cross-site scripting (XSS) (CWE-79) exists in hono.
Check the vendor advisory for the affected versions of hono.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 4.12.14.
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.14ステージング環境で 4.12.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com