CVE-2024-52595

HIGHNVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2024-11-19. NVD baseline CVSS 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2024-0206 (ENISA EUVD) · GHSA-5jfw-gq64-q45f (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

lxml_html_clean is a project for HTML cleaning functionalities copied from lxml.html.clean. Prior to version 0.4.0, the HTML Parser in lxml does not properly handle context-switching for special HTML tags such as `, and . This behavior deviates from how web browsers parse and interpret such tags. Specifically, content in CSS comments is ignored by lxml_html_clean 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 lxml_html_clean in default configuration for sanitizing untrusted HTML content. Users employing the HTML cleaner in a security-sensitive context should upgrade to lxml 0.4.0, which addresses this issue. As a temporary mitigation, users can configure lxml_html_clean with the following settings to prevent the exploitation of this vulnerability. Via remove_tags, one may specify tags to remove - their content is moved to their parents' tags. Via kill_tags, one may specify tags to be removed completely. Via allow_tags, one may restrict the set of permissible tags, excluding context-switching tags like , and `.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2024

Last Modified

November 25, 2024

Advisory Details (3)

Auto-updated Oct 19, 2026
Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

HTML Cleaner allows crafted scripts in special contexts like svg or math to pass through · Advisory · fedora-python/lxml_html_clean · GitHub

https://github.com/fedora-python/lxml_html_clean/security/advisories/GHSA-5jfw-gq64-q45f
GitHub pull request

Scan for JS code also in CSS comments

Fix merged in fedora-python/lxml_html_clean PR #19 on 2024-11-14 — awaiting tagged release

https://github.com/fedora-python/lxml_html_clean/pull/19
GitHub commit

commit c5d816f86eb3 (fedora-python/lxml_html_clean)

Fix landed in fedora-python/lxml_html_clean commit c5d816f86eb3 — awaiting tagged release

https://github.com/fedora-python/lxml_html_clean/commit/c5d816f86eb3707d72a8ecf5f3823e0daa1b3808

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piplxml-html-clean @ 0.4.0 (fixes < 0.4.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lxml-html-clean—
  • every version up to 0.4.1-1: fixed in 0.4.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lxml-html-clean—
  • every version up to 0.4.1-1: fixed in 0.4.1-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
lxml-html-clean0.1.0 ... 0.3.1 (7 versions)
  • every version up to 0.4.0: fixed in 0.4.0
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 214 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-5jfw-gq64-q45f · GitHub severity HIGH · GitHub CVSS 7.7
  3. 2026-11-01 08:11 UTCEG score recompute
  4. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-27 17:19 UTCEG score recompute
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 16:57 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-19 16:00 UTCEG score recompute
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-18 06:52 UTCEG score recompute
  22. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 69 more
  1. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-12 17:39 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-11 21:05 UTCEG score recompute
  5. 2026-10-11 15:57 UTCEG score recompute
  6. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-10 07:55 UTCOSV refresh
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-02 16:20 UTCEG score recompute
  17. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-09-20 17:14 UTCOSV refresh
  28. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-09-17 19:27 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-09-01 17:26 UTCOSV refresh
  46. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-09-01 04:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  50. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  51. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  52. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  53. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  55. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  56. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  57. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  58. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  59. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  60. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  61. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  62. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  63. 2026-08-15 18:37 UTCOSV refresh
  64. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  65. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  66. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  67. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  68. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  69. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-52595?
CVE-2024-52595 is a high-severity vulnerability; its CVE record was published on November 19, 2024. lxml_html_clean is a project for HTML cleaning functionalities copied from lxml.html.clean. Prior to version 0.4.0, 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…
When was the CVE record for CVE-2024-52595 published?
The CVE record for CVE-2024-52595 was published on November 19, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 25, 2024; the record at its source may have been updated since.
Is CVE-2024-52595 actively exploited?
CVE-2024-52595 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-52595?
CVE-2024-52595 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2024-52595?
A fix for CVE-2024-52595 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-52595

Explore →

Is Your Infrastructure Affected by CVE-2024-52595?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs