Which versions of html-sanitizer are affected by CVE-2024-34078?

html-sanitizer (pip) versions < 2.4.2 is affected.

Is there a fix for CVE-2024-34078?

Yes. CVE-2024-34078 is fixed in 2.4.2. Upgrade to this version or later.

Is CVE-2024-34078 exploitable, and should I be worried?

Whether CVE-2024-34078 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 CVE-2024-34078 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 CVE-2024-34078?

Upgrade html-sanitizer to 2.4.2 or later.

CVE-2024-34078 in html-sanitizer

Q: What is CVE-2024-34078?

CVE-2024-34078 is a high-severity security vulnerability in html-sanitizer (pip), affecting versions < 2.4.2. It is fixed in 2.4.2.

Q: Is there a fix for CVE-2024-34078?

Yes. CVE-2024-34078 is fixed in 2.4.2. Upgrade to this version or later.

Q: Is CVE-2024-34078 exploitable, and should I be worried?

Whether CVE-2024-34078 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 CVE-2024-34078 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 CVE-2024-34078?

Upgrade html-sanitizer to 2.4.2 or later.

CVE-2024-34078

CVE-2024-34078 is a high-severity security vulnerability in html-sanitizer (pip), affecting versions < 2.4.2. It is fixed in 2.4.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Arbitrary HTML present after sanitization because of unicode normalization

Workarounds

Set keep_typographic_whitespace=True explicitly, or normalize to NFKC yourself earlier.

Impact

If using keep_typographic_whitespace=False (which is the default), the sanitizer normalizes unicode to the NFKC form at the end. Some unicode characters normalize to chevrons; this allows specially crafted HTML to escape sanitization.

Affected versions

html-sanitizer (< 2.4.2)

Security releases

html-sanitizer → 2.4.2 (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

The problem has been fixed in 2.4.2.

Frequently Asked Questions

What is CVE-2024-34078? CVE-2024-34078 is a high-severity security vulnerability in html-sanitizer (pip), affecting versions < 2.4.2. It is fixed in 2.4.2.
Which versions of html-sanitizer are affected by CVE-2024-34078? html-sanitizer (pip) versions < 2.4.2 is affected.
Is there a fix for CVE-2024-34078? Yes. CVE-2024-34078 is fixed in 2.4.2. Upgrade to this version or later.
Is CVE-2024-34078 exploitable, and should I be worried? Whether CVE-2024-34078 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 CVE-2024-34078 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 CVE-2024-34078? Upgrade html-sanitizer to 2.4.2 or later.