GHSA-69xw-7hcm-h432
MEDIUMGHSA-69xw-7hcm-h432 is a medium-severity (CVSS 4.7) vulnerability in hono. O3 Security confirms whether GHSA-69xw-7hcm-h432 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
hono/jsx has Unvalidated JSX Tag Names that May Allow HTML Injection
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
hononpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | hono | all versions | 4.12.16 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hono. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update hono to 4.12.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-69xw-7hcm-h432 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-69xw-7hcm-h432 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-69xw-7hcm-h432. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-69xw-7hcm-h432 in your dependencies?
O3 detects GHSA-69xw-7hcm-h432 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.