CVE-2019-19450

paraparser in ReportLab before 3.5.31 allows remote code execution because start_unichar in paraparser.py evaluates untrusted user input in a unichar element in a crafted XML document with '<unichar code="' followed by arbitrary Python code, a similar issue to CVE-2019-17626.

Published: 2023-09-20 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2019-19450 is rated High Risk (65.8/100): CVSS Critical severity, with high exploitation likelihood (EPSS 4.45%, 90th percentile). Core evidence: EPSS ranks this CVE among the most likely to be exploited in the near term. Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-19450

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 9.48% 4.45% -5.03%
2 2026-04-19 6.40% 9.48% +3.08%
3 2026-03-04 6.40%

Full EPSS history (46 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-19450

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 5.9 [email protected]

Weakness enumeration for CVE-2019-19450

GitHub Security Advisory for CVE-2019-19450

GHSA-pj98-2xf6-cff5 · Severity: critical · Ecosystem: pip — ReportLab vulnerable to remote code execution via paraparser

OS Trackers for CVE-2019-19450

vendor priority summary link
debian not yet assigned CVE-2019-19450 not yet assigned priority: Debian including 1 source packages (python-reportlab), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2019-19450
redhat high https://access.redhat.com/security/cve/CVE-2019-19450
suse high https://www.suse.com/security/cve/CVE-2019-19450/
ubuntu medium CVE-2019-19450 medium priority: Ubuntu including 1 source packages (python-reportlab), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 8, needs-triage 2, ignored 1, released 1. https://ubuntu.com/security/CVE-2019-19450

Affected software / configurations for CVE-2019-19450

Vendor Product Version Raw CPE
reportlab reportlab < 3.5.31 cpe:2.3:a:reportlab:reportlab:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2019-19450

cvelogic Threat Intelligence