How severe is GHSA-cg48-9hh2-x6mx?

No CVSS score has been assigned to GHSA-cg48-9hh2-x6mx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cg48-9hh2-x6mx?

GHSA-cg48-9hh2-x6mx affects the following packages: preact (npm). Ecosystems affected: npm.

How do I fix GHSA-cg48-9hh2-x6mx?

Update preact to 10.0.0-beta.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cg48-9hh2-x6mx is resolved across your whole dependency graph.

How do I detect GHSA-cg48-9hh2-x6mx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for preact. 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-cg48-9hh2-x6mx 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-cg48-9hh2-x6mx?

O3 pinpoints whether GHSA-cg48-9hh2-x6mx 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-cg48-9hh2-x6mx actively exploited in the wild?

No public exploit code has been indexed for GHSA-cg48-9hh2-x6mx 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-cg48-9hh2-x6mx published, and has it been updated?

GHSA-cg48-9hh2-x6mx was published on September 2, 2020 and was last updated on September 27, 2021. 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-cg48-9hh2-x6mx

GHSA-cg48-9hh2-x6mx is a security vulnerability in preact. O3 Security confirms whether GHSA-cg48-9hh2-x6mx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

HTML Injection in preact

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

preactnpm

28.5Mdownloads / week

Description

Versions of preact 10.x on prerelease tags alpha and beta prior to 10.0.0-beta.1 are vulnerable to HTML Injection. Due to insufficient input validation the package allows attackers to inject JavaScript objects as virtual-dom nodes, which may lead to Cross-Site Scripting. This requires user input parsed with JSON.parse() to be passed directly into JSX without sanitization.

Recommendation

Upgrade to version 10.0.0-beta.1.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`preact`	≥ 10.0.0-alpha.0&&< 10.0.0-beta.1	10.0.0-beta.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for preact. 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 preact to 10.0.0-beta.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cg48-9hh2-x6mx 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-cg48-9hh2-x6mx 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-cg48-9hh2-x6mx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `preact` 10.x on prerelease tags alpha and beta prior to 10.0.0-beta.1 are vulnerable to HTML Injection. Due to insufficient input validation the package allows attackers to inject JavaScript objects as virtual-dom nodes, which may lead to Cross-Site Scripting. This requires user input parsed with `JSON.parse()` to be passed directly into JSX without sanitization. ## Recommendation Upgrade to version 10.0.0-beta.1.

O3 Security · Impact-Aware SCA

Is GHSA-cg48-9hh2-x6mx in your dependencies?

O3 detects GHSA-cg48-9hh2-x6mx 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