CVE-2026-44455: Hono: Unvalidated JSX Tag Names in hono/jsx May Allow HTML Injection

Published May 6, 2026
·
Updated

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 allowlisted tag names are not affected.

Other sources

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.16, 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. This vulnerability is fixed in 4.12.16.

MITRE

Affected Software

2 affected componentsFixes available
npm/hono<4.12.16
4.12.16
Hono Hono Node.js<4.12.16

Event History

May 6, 2026
Advisory Published
via GitHub·11:49 PM
Data Sourced
via GitHub·11:49 PM
DescriptionSeverityWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·02:57 PM
Data Sourced
via MITRE·02:57 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-44455?

CVE-2026-44455 has a moderate severity level due to improper handling of JSX element tag names that can lead to XSS vulnerabilities.

2

How do I fix CVE-2026-44455?

To fix CVE-2026-44455, upgrade the hono package to version 4.12.16 or higher.

3

What type of input does CVE-2026-44455 affect?

CVE-2026-44455 is affected by untrusted input that is used as tag names in the jsx() or createElement() APIs.

4

Which software is affected by CVE-2026-44455?

CVE-2026-44455 affects versions of the hono package prior to 4.12.16.

5

What are the potential risks of CVE-2026-44455?

The risks associated with CVE-2026-44455 include the possibility of executing malicious scripts within client browsers due to improper sanitization.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203