CVE-2014-3146

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 4.3%, top 11% 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, nvd
Weaponized
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 6%CVSS: 6.1Exploit: NoneExposed: 0

A fix is available — apply it.

Incomplete blacklist vulnerability in the lxml.html.clean module in lxml before 3.3.5 allows remote attackers to conduct cross-site scripting (XSS) attacks via control characters in the link scheme to the clean_html function.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
92.8%
KEV
Not listed

Published

May 14, 2014

Last Modified

May 6, 2026

Advisory Details (8)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

[SECURITY] [DSA 2941-1] lxml security update

http://www.debian.org/security/2014/dsa-2941
generic

About Secunia Research | Flexera

http://secunia.com/advisories/59008
generic

About Secunia Research | Flexera

http://secunia.com/advisories/58744
generic

About Secunia Research | Flexera

http://secunia.com/advisories/58013
generic

Full Disclosure: Re: lxml (python lib) vulnerability

http://seclists.org/fulldisclosure/2014/Apr/319
generic

Full Disclosure: lxml (python lib) vulnerability

http://seclists.org/fulldisclosure/2014/Apr/210
generic

lxml changelog

http://lxml.de/3.3/changes-3.3.5.html
generic

Mageia Advisory: MGASA-2014-0218 - Updated python-lxml package fix CVE-2014-3146

http://advisories.mageia.org/MGASA-2014-0218.html

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-lxml (3.3.3-1ubuntu0.1) @ trusty2026-05-28ubuntu

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
lxml0.9 ... 3.3.4 (101 versions)3.3.5—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-05 00:26 UTCOSV refresh
  6. 2026-07-04 06:27 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-27 03:05 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:02 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-23 21:30 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:22 UTCEPSS rescore
  22. 2026-06-22 14:22 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-19 19:23 UTCEPSS rescore
Show 50 more
  1. 2026-06-18 17:49 UTCEPSS rescore
  2. 2026-06-18 17:49 UTCEPSS rescore
  3. 2026-06-17 17:49 UTCEPSS rescore
  4. 2026-06-17 17:49 UTCEPSS rescore
  5. 2026-06-16 17:50 UTCEPSS rescore
  6. 2026-06-16 17:49 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-16 12:13 UTCOSV refresh
  9. 2026-06-14 23:14 UTCEPSS rescore
  10. 2026-06-13 22:57 UTCEPSS rescore
  11. 2026-06-12 23:08 UTCEPSS rescore
  12. 2026-06-11 13:57 UTCEPSS rescore
  13. 2026-06-10 22:15 UTCEPSS rescore
  14. 2026-06-08 14:14 UTCEPSS rescore
  15. 2026-06-06 13:45 UTCEPSS rescore
  16. 2026-06-06 13:45 UTCEPSS rescore
  17. 2026-06-05 22:44 UTCEPSS rescore
  18. 2026-06-05 06:08 UTCEPSS rescore
  19. 2026-06-05 06:08 UTCEPSS rescore
  20. 2026-06-04 13:09 UTCEPSS rescore
  21. 2026-06-04 13:09 UTCEPSS rescore
  22. 2026-06-02 20:10 UTCEPSS rescore
  23. 2026-06-02 20:10 UTCEPSS rescore
  24. 2026-06-01 13:49 UTCEPSS rescore
  25. 2026-06-01 13:49 UTCEPSS rescore
  26. 2026-05-31 22:28 UTCEPSS rescore
  27. 2026-05-31 22:28 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-31 00:14 UTCEPSS rescore
  30. 2026-05-29 13:41 UTCEPSS rescore
  31. 2026-05-28 18:58 UTCEG score recompute
  32. 2026-05-28 18:58 UTCVendor advisory
  33. 2026-05-28 13:42 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-26 15:31 UTCOSV refresh
  39. 2026-05-26 07:16 UTCEPSS rescore
  40. 2026-05-24 16:43 UTCEPSS rescore
  41. 2026-05-22 21:15 UTCEPSS rescore
  42. 2026-05-22 21:15 UTCEPSS rescore
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-21 22:39 UTCEPSS rescore
  45. 2026-05-20 22:37 UTCEPSS rescore
  46. 2026-05-20 22:37 UTCEPSS rescore
  47. 2026-05-20 22:37 UTCEPSS rescore
  48. 2026-05-20 11:21 UTCEPSS rescore
  49. 2026-05-20 11:21 UTCEPSS rescore
  50. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-39155✓ verified
    First seen Apr 15, 2014

    lxml - 'clean_html' Security Bypass

    Open source ↗

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2014-3146?
CVE-2014-3146 is a medium vulnerability published on May 14, 2014. Incomplete blacklist vulnerability in the lxml.html.clean module in lxml before 3.3.5 allows remote attackers to conduct cross-site scripting (XSS) attacks via control characters in the link scheme to the clean_html function.
When was CVE-2014-3146 disclosed?
CVE-2014-3146 was first published in the National Vulnerability Database on May 14, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-3146 actively exploited?
CVE-2014-3146 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2014-3146?
CVE-2014-3146 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2014-3146?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-3146, 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-2014-3146

Explore →

Is Your Infrastructure Affected by CVE-2014-3146?

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

Start Free Scan →Browse All CVEs