GHSA-h6p3-p4vx-wr8q — dompurify
GHSA-h6p3-p4vx-wr8q is a security vulnerability in dompurify. A fix is available for dompurify — see the affected versions and patch details below.
dompurify vulnerable to Cross-site Scripting
Real-World Exposure
dompurifyReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
dompurify prior to version 2.2.3 is vulnerable to a cross-site scripting problem caused by nested headlines.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | dompurify | all versions | 2.2.3pip install --upgrade 'dompurify==2.2.3' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompurify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dompurify to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6p3-p4vx-wr8q 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-h6p3-p4vx-wr8q can be triaged on real exposure rather than presence alone.
Tailored to GHSA-h6p3-p4vx-wr8q. 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-h6p3-p4vx-wr8q in your dependencies?
O3 Security finds GHSA-h6p3-p4vx-wr8q across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.