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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cg48-9hh2-x6mx can be triaged on real exposure rather than presence alone.

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

Not in CISA KEV

GHSA-cg48-9hh2-x6mx — preact

Fix: developit/preact#1528

GHSA-cg48-9hh2-x6mx is a security vulnerability in preact. A fix is available for preact — see the affected versions and patch details below.

HTML Injection in preact

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

preactnpm

24.2Mdownloads / 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`npm install preact@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cg48-9hh2-x6mx can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-cg48-9hh2-x6mx across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works