What is GHSA-H6P3-P4VX-WR8Q?

GHSA-H6P3-P4VX-WR8Q is a medium-severity security vulnerability in dompurify (pip), affecting versions < 2.2.3. It is fixed in 2.2.3.

Which versions of dompurify are affected by GHSA-H6P3-P4VX-WR8Q?

dompurify (pip) versions < 2.2.3 is affected.

Is there a fix for GHSA-H6P3-P4VX-WR8Q?

Yes. GHSA-H6P3-P4VX-WR8Q is fixed in 2.2.3. Upgrade to this version or later.

Is GHSA-H6P3-P4VX-WR8Q exploitable, and should I be worried?

Whether GHSA-H6P3-P4VX-WR8Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-H6P3-P4VX-WR8Q is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-H6P3-P4VX-WR8Q in dompurify

Q: Which versions of dompurify are affected by GHSA-H6P3-P4VX-WR8Q?

dompurify (pip) versions < 2.2.3 is affected.

Q: Is there a fix for GHSA-H6P3-P4VX-WR8Q?

Yes. GHSA-H6P3-P4VX-WR8Q is fixed in 2.2.3. Upgrade to this version or later.

Q: Is GHSA-H6P3-P4VX-WR8Q exploitable, and should I be worried?

Whether GHSA-H6P3-P4VX-WR8Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-H6P3-P4VX-WR8Q is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-H6P3-P4VX-WR8Q?

Upgrade dompurify to 2.2.3 or later.

Summary

dompurify vulnerable to Cross-site Scripting

dompurify prior to version 2.2.3 is vulnerable to a cross-site scripting problem caused by nested headlines.

Impact

Affected versions

dompurify (< 2.2.3)

Security releases

dompurify → 2.2.3 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade dompurify to 2.2.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-H6P3-P4VX-WR8Q? GHSA-H6P3-P4VX-WR8Q is a medium-severity security vulnerability in dompurify (pip), affecting versions < 2.2.3. It is fixed in 2.2.3.
Which versions of dompurify are affected by GHSA-H6P3-P4VX-WR8Q? dompurify (pip) versions < 2.2.3 is affected.
Is there a fix for GHSA-H6P3-P4VX-WR8Q? Yes. GHSA-H6P3-P4VX-WR8Q is fixed in 2.2.3. Upgrade to this version or later.
Is GHSA-H6P3-P4VX-WR8Q exploitable, and should I be worried? Whether GHSA-H6P3-P4VX-WR8Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-H6P3-P4VX-WR8Q is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-H6P3-P4VX-WR8Q? Upgrade dompurify to 2.2.3 or later.

Other vulnerabilities in dompurify

CVE-IDSeverityPackage summary

GHSA-55Q2-FJHQ-7XH7Mediumdompurify: DOMPurify: IN_PLACE hook removal leaves a detached subtree executable, causing XSS GHSA-C2J3-45GR-MQC4Lowdompurify: DOMPurify: `CUSTOM_ELEMENT_HANDLING` bypasses `afterSanitizeElements` for allowed custom elements.CVE-2026-65898Mediumdompurify: DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution…CVE-2026-65899Lowdompurify: DOMPurify: Trusted Types policy survives `clearConfig()` and can poison later `RETURN_TRUSTED_TYPE` output CVE-2026-65900Lowdompurify: DOMPurify: SAFE_FOR_TEMPLATES bypass - template expressions survive sanitization inside <template> content when using DOM output modes