Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-57qw-cc2g-pv5p

MEDIUMFix: lxml/lxml#273

GHSA-57qw-cc2g-pv5p is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in lxml. 4 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-57qw-cc2g-pv5p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

lxml Cross-site Scripting Via Control Characters

Also known asCVE-2014-3146PYSEC-2014-9
Published
May 14, 2022
Updated
Sep 30, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
4 known
Exploitation data as of Sep 30, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍lxml

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIlxmlall versions3.3.5
Exploits & PoCs
4

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-39155remotelinux✓ Verified

lxml - 'clean_html' Security Bypass

by Maksim Kochkin · Apr 15, 2014

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lxml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update lxml to 3.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-57qw-cc2g-pv5p is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-57qw-cc2g-pv5p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-57qw-cc2g-pv5p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-57qw-cc2g-pv5p in your dependencies?

O3 detects GHSA-57qw-cc2g-pv5p across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-57qw-cc2g-pv5p: lxml Cross-site… | O3 Security