cve.bz

CVE-2026-126359

Hono: `css` helper does not escape a closing tag split between the template and an interpolated value, allowing HTML injection

3.4 lowFix available

Low (3.4) in honojs hono. Fixed in hono 4.13.16.

On this page
Hono is a Web application framework that provides support for any JavaScript runtime. From 3.12.0 until 4.13.16, the css helper in hono/css escapes interpolated string values separately and therefore fails to neutralize a closing style tag when < ends the template text or a preceding value and / begins the next attacker-controlled value. During server-side rendering, the combined output can close the <Style /> element early and cause the remainder of the interpolated value to be interpreted as HTML. Applications that place an untrusted string immediately after < in a css template, including adjacent untrusted interpolations, can expose viewers to attacker-controlled HTML or script and information accessible to that page. Other uses of the css helper are not affected. This issue is fixed in version 4.13.16.

Severity

CVSS 3.1

3.4 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Assigned by
GitHub_M (CNA)
NVD analysis
Not in the NVD yet
Record from
the CVE List, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126359 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126359?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126359?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126359 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126359

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126359](https://cve.bz/cve/badge/CVE-2026-126359.svg)](https://cve.bz/cve/CVE-2026-126359)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126359"><img src="https://cve.bz/cve/badge/CVE-2026-126359.svg" alt="CVE-2026-126359"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
honojs hono>= 3.12.0, < 4.13.16

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3gg2-335m-rxc6npmhono>=3.12.0 <4.13.164.13.16

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON