CVE-2014-3146

MEDIUMNVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 6.3% (93rd percentile of EPSS-scored CVEs). 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.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 6.3%CVSS: 6.1Exploit: Exploit-DB (verified) · public exploitExposed services: Not assessed

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.1MEDIUMmedium confidence
EG Risk
53
EG Risk 53/100CISA SSVC

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
Severity61% × 45%
Exploitation65% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
6.3%
EPSS %ILE
93rd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 14, 2014

Last Modified

May 6, 2026

Advisory Details (8)

Auto-updated May 7, 2026
Patch available.
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 / EcosystemFix (by version range) / 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

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
lxml—
  • every version up to 3.3.5-1: fixed in 3.3.5-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lxml—
  • every version up to 3.3.5-1: fixed in 3.3.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lxml—
  • every version up to 3.3.5-1: fixed in 3.3.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lxml—
  • every version up to 3.3.5-1: fixed in 3.3.5-1
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
lxml2.2.8-2
  • every version up to 2.2.8-2+deb6u1: fixed in 2.2.8-2+deb6u1
—
Debian:7(1)
PackageVulnerable rangeFix by version rangeDependents
lxml2.3.2-1
  • every version up to 2.3.2-1+deb7u1: fixed in 2.3.2-1+deb7u1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
lxml0.9 ... 3.3.4 (101 versions)
  • every version up to 3.3.5: fixed in 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 7× in last 7d / 22× 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.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-10-10 19:54 UTCEPSS rescore
  2. 2026-10-09 20:01 UTCEPSS rescore
  3. 2026-10-08 16:34 UTCEPSS rescore
  4. 2026-10-07 23:39 UTCEPSS rescore
  5. 2026-10-06 15:11 UTCEPSS rescore
  6. 2026-10-05 17:38 UTCEPSS rescore
  7. 2026-10-04 23:17 UTCEPSS rescore
  8. 2026-10-03 14:21 UTCEPSS rescore
  9. 2026-10-01 19:43 UTCEPSS rescore
  10. 2026-09-30 14:58 UTCEPSS rescore
  11. 2026-09-30 00:22 UTCEG score recompute
  12. 2026-09-29 21:41 UTCOSV refresh
  13. 2026-09-28 13:45 UTCEPSS rescore
  14. 2026-09-27 13:39 UTCEPSS rescore
  15. 2026-09-26 15:53 UTCEPSS rescore
  16. 2026-09-20 20:08 UTCEPSS rescore
  17. 2026-09-18 19:21 UTCEPSS rescore
  18. 2026-09-17 19:21 UTCEPSS rescore
  19. 2026-09-17 19:21 UTCEPSS rescore
  20. 2026-09-15 03:04 UTCEPSS rescore
  21. 2026-09-12 14:55 UTCEPSS rescore
  22. 2026-09-11 09:31 UTCEPSS rescore
  23. 2026-09-10 16:53 UTCOSV refresh
  24. 2026-09-07 15:56 UTCEPSS rescore
  25. 2026-09-06 13:42 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 15:23 UTCEPSS rescore
  2. 2026-09-04 13:55 UTCEPSS rescore
  3. 2026-09-02 14:07 UTCEPSS rescore
  4. 2026-09-01 13:48 UTCEPSS rescore
  5. 2026-08-30 19:12 UTCEPSS rescore
  6. 2026-08-28 21:34 UTCEPSS rescore
  7. 2026-08-27 14:20 UTCEPSS rescore
  8. 2026-08-26 14:41 UTCEPSS rescore
  9. 2026-08-25 13:44 UTCEPSS rescore
  10. 2026-08-23 10:52 UTCOSV refresh
  11. 2026-08-21 23:44 UTCEPSS rescore
  12. 2026-08-20 22:50 UTCEPSS rescore
  13. 2026-08-19 16:59 UTCEPSS rescore
  14. 2026-08-18 13:43 UTCEPSS rescore
  15. 2026-08-16 14:51 UTCEPSS rescore
  16. 2026-08-16 02:09 UTCEPSS rescore
  17. 2026-08-15 01:25 UTCEPSS rescore
  18. 2026-08-12 13:46 UTCEPSS rescore
  19. 2026-08-09 13:42 UTCEPSS rescore
  20. 2026-08-08 16:31 UTCEPSS rescore
  21. 2026-08-07 16:21 UTCEPSS rescore
  22. 2026-08-07 12:57 UTCOSV refresh
  23. 2026-08-06 13:42 UTCEPSS rescore
  24. 2026-08-05 19:12 UTCEPSS rescore
  25. 2026-08-04 15:04 UTCEPSS rescore
  26. 2026-08-02 02:22 UTCEPSS rescore
  27. 2026-08-01 04:11 UTCEPSS rescore
  28. 2026-07-30 16:23 UTCEPSS rescore
  29. 2026-07-30 01:26 UTCEPSS rescore
  30. 2026-07-28 15:31 UTCEPSS rescore
  31. 2026-07-24 14:13 UTCEPSS rescore
  32. 2026-07-23 14:14 UTCEPSS rescore
  33. 2026-07-23 01:12 UTCEG score recompute
  34. 2026-07-23 00:16 UTCEG score recompute
  35. 2026-07-22 21:54 UTCEG score recompute
  36. 2026-07-22 14:04 UTCEPSS rescore
  37. 2026-07-22 05:48 UTCOSV refresh
  38. 2026-07-21 15:21 UTCEPSS rescore
  39. 2026-07-21 15:21 UTCEPSS rescore
  40. 2026-07-20 17:03 UTCEPSS rescore
  41. 2026-07-19 14:27 UTCEPSS rescore
  42. 2026-07-19 02:26 UTCEPSS rescore
  43. 2026-07-19 02:26 UTCEPSS rescore
  44. 2026-07-18 10:00 UTCEPSS rescore
  45. 2026-07-16 16:59 UTCEPSS rescore
  46. 2026-07-15 16:54 UTCEPSS rescore
  47. 2026-07-15 16:54 UTCEPSS rescore
  48. 2026-07-15 01:56 UTCEPSS rescore
  49. 2026-07-13 22:26 UTCEPSS rescore
  50. 2026-07-13 06:08 UTCEPSS rescore
  51. 2026-07-12 05:42 UTCEPSS rescore
  52. 2026-07-12 05:42 UTCEPSS rescore
  53. 2026-07-11 08:23 UTCEPSS rescore
  54. 2026-07-09 19:05 UTCEPSS rescore
  55. 2026-07-08 15:10 UTCEPSS rescore
  56. 2026-07-07 13:42 UTCEPSS rescore
  57. 2026-07-06 16:24 UTCEPSS rescore
  58. 2026-07-06 02:20 UTCEPSS rescore
  59. 2026-07-05 02:26 UTCEPSS rescore
  60. 2026-07-05 00:26 UTCOSV refresh
  61. 2026-07-04 06:27 UTCEPSS rescore
  62. 2026-07-01 15:02 UTCEPSS rescore
  63. 2026-07-01 15:02 UTCEPSS rescore
  64. 2026-06-30 23:19 UTCEPSS rescore
  65. 2026-06-30 23:19 UTCEPSS rescore
  66. 2026-06-29 14:02 UTCEPSS rescore
  67. 2026-06-28 04:53 UTCEPSS rescore
  68. 2026-06-28 04:53 UTCEPSS rescore
  69. 2026-06-27 03:05 UTCEPSS rescore
  70. 2026-06-25 13:47 UTCEPSS rescore
  71. 2026-06-25 13:47 UTCEPSS rescore
  72. 2026-06-24 14:02 UTCEPSS rescore
  73. 2026-06-24 14:02 UTCEPSS rescore
  74. 2026-06-23 21:30 UTCEPSS rescore
  75. 2026-06-23 21:30 UTCEPSS rescore

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-39155✓ verified
    Published Apr 15, 2014

    lxml - 'clean_html' Security Bypass

    Open source ↗

Related CVEs(same product)

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 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. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 6.3% probability of exploitation in the next 30 days (93rd percentile of EPSS-scored CVEs).
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?
A fix for CVE-2014-3146 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-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.

Book a Demo →Browse All CVEs