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

GHSA-qpg2-vx7j-3869 reportlab

CRITICAL

GHSA-qpg2-vx7j-3869 is a critical-severity (CVSS 9.8) CWE-91 vulnerability in reportlab. 1 public exploit reference exists, so weaponization risk is real. A fix is available for reportlab — see the affected versions and patch details below.

XML Injection in ReportLab

Also known asCVE-2019-17626PYSEC-2019-117
Published
May 24, 2022
Updated
Oct 26, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qpg2-vx7j-3869.

EPSS Exploitation Probability

via FIRST.org ↗
10.2%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-qpg2-vx7j-3869 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐍reportlab

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

ReportLab through 3.5.26 allows remote code execution because of toColor(eval(arg)) in colors.py, as demonstrated by a crafted XML document with '<span color="' followed by arbitrary Python code.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIreportlaball versions3.5.28pip install --upgrade 'reportlab==3.5.28'
Exploits & PoCs
1

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

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for reportlab, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update reportlab to 3.5.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qpg2-vx7j-3869 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qpg2-vx7j-3869 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qpg2-vx7j-3869. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability will not be fixed in Red Hat Quay because it only affects a non-supported feature which is disabled behind a feature flag.

ProductFixed inAdvisory
Red Hat Enterprise Linux 6python-reportlab-0:2.3-3.el6_10.1RHSA-2020:0197
Red Hat Enterprise Linux 7python-reportlab-0:2.5-9.el7_7.1RHSA-2020:0195
Red Hat Enterprise Linux 8python-reportlab-0:3.4.0-6.el8_1.2RHSA-2020:0201
Red Hat Enterprise Linux 8.0 Update Services for SAP Solutionspython-reportlab-0:3.4.0-6.el8_0.2RHSA-2020:0230
UbuntuCRITICAL

Frequently Asked Questions

ReportLab through 3.5.26 allows remote code execution because of toColor(eval(arg)) in colors.py, as demonstrated by a crafted XML document with '<span color="' followed by arbitrary Python code.
O3 Security · Impact-Aware SCA

Is GHSA-qpg2-vx7j-3869 in your dependencies?

O3 Security finds GHSA-qpg2-vx7j-3869 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-qpg2-vx7j-3869: reportlab (Critical 9.8) | O3 Security