Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7amended

HTML Cleaner allows crafted scripts in special contexts like svg or math to pass through

CVE-2024-52595GHSA-5jfw-gq64-q45f

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (lxml-html-clean 0.4.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:H
EPSS
  • CVE-2024-52595: 0.51% estimated exploitation activity in the next 30 days; percentile 43.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact The HTML Parser in lxml does not properly handle context-switching for special HTML tags such as <svg, <math and <noscript. This behavior deviates from how web browsers parse and interpret such tags. Specifically, content in CSS comments is ignored by lxmlhtmlclean but may be interpreted differently by web browsers, enabling malicious scripts to bypass the cleaning process. This vulnerability could lead to Cross-Site Scripting (XSS) attacks, compromising the security of users relying on lxmlhtmlclean in default configuration for sanitizing untrusted HTML content. Patches Users employing the HTML cleaner in a security-sensitive context should upgrade to lxml 0.4.0, which addresses this issue. Workarounds As a temporary mitigation, users can configure lxmlhtmlclean with the following settings to prevent the exploitation of this vulnerability: removetags: Specify tags to remove - their content is moved to their parents' tags. killtags: Specify tags to be removed completely.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-5jfw-gq64-q45f

  2. Revision 1 · created ·

    Published from osv record GHSA-5jfw-gq64-q45f

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52595

Advisory: HTML Cleaner allows crafted scripts in special contexts like svg or math to pass through
IDs: CVE-2024-52595, GHSA-5jfw-gq64-q45f
Record: https://patchnext.com/advisories/cve-2024-52595 (revision 2, source checked 26 Oct 2026, 13:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: lxml-html-clean 0.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI lxml-html-clean: affected < 0.4.0; fixed in 0.4.0

## Suggested inspection (read-only)
- `python -m pip show lxml-html-clean`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lxml-html-clean.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5jfw-gq64-q45f (OSV record GHSA-5jfw-gq64-q45f lists affected ranges: PyPI lxml-html-clean >=0 <0.4.0 (fixed))
- Verified: https://github.com/advisories/GHSA-5jfw-gq64-q45f (GitHub-reviewed advisory GHSA-5jfw-gq64-q45f lists affected ranges: PyPI lxml-html-clean >=0 <0.4.0)

Commands are suggestions: review each one before running it.

Loading voting…