How severe is GHSA-qp7p-654g-cw7p?

GHSA-qp7p-654g-cw7p has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qp7p-654g-cw7p?

GHSA-qp7p-654g-cw7p affects the following packages: hono (npm). Ecosystems affected: npm.

How do I fix GHSA-qp7p-654g-cw7p?

Update hono to 4.12.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qp7p-654g-cw7p is resolved across your whole dependency graph.

How do I detect GHSA-qp7p-654g-cw7p in my npm dependencies?

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.

How do I mitigate GHSA-qp7p-654g-cw7p if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-qp7p-654g-cw7p?

O3 pinpoints whether GHSA-qp7p-654g-cw7p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qp7p-654g-cw7p actively exploited in the wild?

No public exploit code has been indexed for GHSA-qp7p-654g-cw7p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qp7p-654g-cw7p published, and has it been updated?

GHSA-qp7p-654g-cw7p was published on May 9, 2026 and was last updated on May 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-qp7p-654g-cw7p

MEDIUM

GHSA-qp7p-654g-cw7p is a medium-severity (CVSS 4.3) vulnerability in hono. O3 Security confirms whether GHSA-qp7p-654g-cw7p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Hono has CSS Declaration Injection via Style Object Values in JSX SSR

Also known asCVE-2026-44458

Published

May 9, 2026

Updated

May 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

hononpm

56.6Mdownloads / week

Description

Summary

The JSX renderer escapes style attribute object values for HTML but not for CSS. Untrusted input in a style object value or property name can therefore inject additional CSS declarations into the rendered style attribute. The impact is limited to CSS and does not allow JavaScript execution or HTML attribute breakout.

Details

style object values are serialized into a CSS declaration list and escaped for HTML attribute context only. Characters that act as CSS declaration boundaries — such as ;, comment markers, quoted strings, and block delimiters — are valid in HTML attribute content and can extend a value beyond its assigned property.

This issue arises when untrusted input is interpolated into a JSX style object and rendered server-side.

Impact

An attacker who can control the value or property name of a style object may inject arbitrary CSS declarations. This may lead to:

Visual manipulation of the page, including full-viewport overlays usable for phishing
Outbound requests to attacker-controlled hosts via CSS resource references such as url(...)
Hijacking of UI affordances through layout, positioning, or visibility changes

This issue affects applications that render JSX on the server with style object values or property names derived from untrusted input.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`hono`	all versions	4.12.18

Detection & mitigation playbook

Open-source dependency

Detect
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.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qp7p-654g-cw7p 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-qp7p-654g-cw7p 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-qp7p-654g-cw7p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The JSX renderer escapes `style` attribute object values for HTML but not for CSS. Untrusted input in a `style` object value or property name can therefore inject additional CSS declarations into the rendered `style` attribute. The impact is limited to CSS and does not allow JavaScript execution or HTML attribute breakout. ### Details `style` object values are serialized into a CSS declaration list and escaped for HTML attribute context only. Characters that act as CSS declaration boundaries — such as `;`, comment markers, quoted strings, and block delimiters — are valid in HTML

O3 Security · Impact-Aware SCA

Is GHSA-qp7p-654g-cw7p in your dependencies?

O3 detects GHSA-qp7p-654g-cw7p across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works