Skip to content
Web

CVE-2026-49825

8.2
High
EPSS 0.24%Patch availableAug 22, 2026

Missing xlink:href in lxml enables URL bypass and XSS via embedded SVG/MathML.

common questions

Is CVE-2026-49825 being exploited?

Not confirmed. CVE-2026-49825 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-49825?

CVE-2026-49825 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-49825?

Yes. A fix has been recorded for CVE-2026-49825. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49825 affect?

CVE-2026-49825 affects lxml < 6.1.1, lxml_html_clean < 0.4.5, Python apps using lxml for HTML/SVG/MathML sanitization. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49825?

Upgrade lxml>=6.1.1 and lxml_html_clean>=0.4.5; sanitize/validate SVG/MathML inputs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
lxml < 6.1.1lxml_html_clean < 0.4.5Python apps using lxml for HTML/SVG/MathML sanitization
impact

URL bypass in embedded SVG/MathML leading to XSS, enabling script execution or phishing in apps rendering untrusted HTML.

action required

Patch when possible

affected versions
lxml lxml
  • affected< 6.1.1
fedora-python lxml_html_clean
  • affected< 0.4.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free