Vulnerability in hono (CVE-2026-44455)
Summary
Vulnerability in hono (CVE-2026-44455). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.12.16 or later.
Original description
The description as published by the source.
Summary
Improper handling of JSX element tag names in hono/jsx allowed unvalidated tag names to be directly inserted into the generated HTML output.
When untrusted input is used as a tag name via the programmatic jsx() or createElement() APIs during server-side rendering, specially crafted values may break out of the intended element context and inject unintended HTML.
Details
When rendering JSX elements to HTML strings, attribute values are escaped and attribute names are validated. However, element tag names were previously inserted into the output without validation.
If a tag name contains characters such as <, >, quotes, or whitespace, it may alter the structure of the generated HTML.
For example, malformed tag names can:
- Break out of the intended element and introduce unintended HTML elements
- Inject attributes or event handlers into the rendered output
This issue arises when untrusted input (such as query parameters or database content) is used as JSX tag names via jsx() or createElement() during server-side rendering.
Impact
An attacker who can control tag names used in JSX rendering may inject unintended HTML into the generated output.
This may lead to:
- Injection of unexpected HTML elements or attributes
- Corruption of the HTML structure
- Cross-site scripting (XSS) when combined with unsafe usage patterns
This issue only affects applications that construct JSX tag names from untrusted input. Applications using static or allowli…
Source: NIST National Vulnerability Database 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-44455 has been found in hono.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: upgrade hono to 4.12.16 or later.
If unsure, ask your IT team or search "hono CVE-2026-44455" on the vendor's site.
CVE-2026-44455 (hono) — CWE-74 / CVSS v3 4.7
Attack vector: remote (network-reachable) / unauthenticated
Patched: 4.12.16 — 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-74) exists in hono.
Check the vendor advisory for the affected versions of hono.
Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.
Update to 4.12.16.
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.16ステージング環境で 4.12.16 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com