CVE-2026-49825

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this weekElevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

A fix is available — apply it.

lxml is a library for processing XML and HTML in the Python language. Prior to 6.1.1, link attributes in `lxml.html.defs.link_attrs were missing xlink:href`, which can be used for URL bypass attacks in embedded SVG/MathML/etc. content. This vulnerability was fixed in lxml 6.1.1 and lxml_html_clean 0.4.5.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

July 8, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 20, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

lxml-6.1.1

Patch available: lxml/lxml lxml-6.1.1

https://github.com/lxml/lxml/releases/tag/lxml-6.1.1
github_commit

commit 5927a6d5e851 (lxml/lxml)

Fix landed in lxml/lxml commit 5927a6d5e851 — awaiting tagged release

https://github.com/lxml/lxml/commit/5927a6d5e851845140975d99b65461e255caaab0
github_commit

commit 322357ac61c6 (fedora-python/lxml_html_clean)

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

https://github.com/fedora-python/lxml_html_clean/commit/322357ac61c6cf80fcbaba53b4e92e31f3ded9f2
github Patch Available

javascript: URL bypass in Cleaner via xlink:href · Advisory · fedora-python/lxml_html_clean · GitHub

https://github.com/fedora-python/lxml_html_clean/security/advisories/GHSA-4jhm-jv67-739f

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpython-lxml-0:4.2.3-5.el8_102026-09-16redhat
redhatpython-lxml-0:4.6.5-3.el9_2.12026-09-14redhat
redhatpython-lxml-0:4.6.5-3.el9_4.12026-09-14redhat
redhatpython-lxml-0:4.6.5-3.el9_6.12026-09-14redhat
redhatpython-lxml-0:4.6.5-3.el9_8.12026-09-09redhat
redhatpython3.12-lxml-0:4.9.3-2.el9_8.12026-09-09redhat

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

(6 across 4 ecosystems)
Debian:13(2)
PackageVulnerable rangeFixed inDependents
lxml5.4.0-1, 6.0.1-1, 6.0.2-1, 6.1.0-1, 7.0.0~a2-1
lxml-html-clean0.4.2-1, 0.4.3-1, 0.4.4-1, 0.4.4-1~deb13u1, 0.4.5-1
Debian:14(2)
PackageVulnerable rangeFixed inDependents
lxml5.4.0-1, 6.0.1-1, 6.0.2-1, 6.1.0-1, 7.0.0~a2-1
lxml-html-clean0.4.2-1, 0.4.3-1, 0.4.4-1, 0.4.4-1~deb13u1, 0.4.5-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
lxml4.9.2-1 ... 7.0.0~a2-1 (16 versions)
PyPI(1)
PackageVulnerable rangeFixed inDependents
lxml-html-clean0.1.0 ... 0.4.4 (12 versions)0.4.5

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 14× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 20:11 UTCEG score recompute
  2. 2026-09-18 20:11 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 05:42 UTCEG score recompute
  5. 2026-09-18 05:42 UTCVendor advisory
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-14 11:15 UTCVendor advisory
  9. 2026-09-13 23:48 UTCEG score recompute
  10. 2026-09-13 23:48 UTCVendor advisory
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-13 08:23 UTCEG score recompute
  13. 2026-09-13 08:23 UTCVendor advisory
  14. 2026-09-12 14:54 UTCVendor advisory
  15. 2026-09-12 03:31 UTCEG score recompute
  16. 2026-09-12 03:31 UTCVendor advisory
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:01 UTCEPSS rescore
  21. 2026-09-06 14:02 UTCEG score recompute
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-05 22:46 UTCEG score recompute
  24. 2026-09-04 05:06 UTCEPSS rescore
  25. 2026-09-02 14:12 UTCEPSS rescore
Show 22 more
  1. 2026-09-01 13:54 UTCEPSS rescore
  2. 2026-09-01 04:40 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 07:28 UTCEG score recompute
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 01:24 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 14:48 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 15:23 UTCEG score recompute
  12. 2026-08-23 05:01 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 04:45 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 17:22 UTCEG score recompute
  17. 2026-08-21 16:51 UTCEG score recompute
  18. 2026-08-20 15:29 UTCEG score recompute
  19. 2026-07-30 09:56 UTCEG score recompute
  20. 2026-07-26 12:25 UTCEG score recompute
  21. 2026-07-23 03:18 UTCEG score recompute
  22. 2026-07-08 20:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49825?
CVE-2026-49825 is a high vulnerability published on July 8, 2026. lxml is a library for processing XML and HTML in the Python language. Prior to 6.1.1, link attributes in lxml.html.defs.linkattrs were missing xlink:href, which can be used for URL bypass attacks in embedded SVG/MathML/etc. content. This vulnerability was fixed in lxml 6.1.1 and lxmlhtml_clean…
When was CVE-2026-49825 disclosed?
CVE-2026-49825 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49825 actively exploited?
CVE-2026-49825 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.6% of all scored CVEs.
What is the CVSS score of CVE-2026-49825?
CVE-2026-49825 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-49825?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49825, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49825

Explore →

Is Your Infrastructure Affected by CVE-2026-49825?

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