How severe is GHSA-mx3p-fhpw-x6rv?

No CVSS score has been assigned to GHSA-mx3p-fhpw-x6rv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mx3p-fhpw-x6rv?

GHSA-mx3p-fhpw-x6rv affects the following packages: tecnickcom/tcpdf (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-mx3p-fhpw-x6rv?

Update tecnickcom/tcpdf to 6.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mx3p-fhpw-x6rv is resolved across your whole dependency graph.

How do I detect GHSA-mx3p-fhpw-x6rv in my Packagist dependencies?

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

How do I mitigate GHSA-mx3p-fhpw-x6rv if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-mx3p-fhpw-x6rv?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mx3p-fhpw-x6rv can be triaged on real exposure rather than presence alone.

Is GHSA-mx3p-fhpw-x6rv actively exploited in the wild?

No public exploit code has been indexed for GHSA-mx3p-fhpw-x6rv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mx3p-fhpw-x6rv?

GHSA-mx3p-fhpw-x6rv has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mx3p-fhpw-x6rv?

GHSA-mx3p-fhpw-x6rv is classified as CWE-1333 (CWE-1333). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mx3p-fhpw-x6rv published, and has it been updated?

GHSA-mx3p-fhpw-x6rv was published on April 19, 2024 and was last updated on November 4, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-mx3p-fhpw-x6rv — tecnickcom/tcpdf

Fix: tecnickcom/TCPDF@05f3a28

GHSA-mx3p-fhpw-x6rv is a CWE-1333 vulnerability in tecnickcom/tcpdf. A fix is available for tecnickcom/tcpdf — see the affected versions and patch details below.

TCPDF vulnerable to Regular Expression Denial of Service

Also known asCVE-2024-22640

Published

Apr 19, 2024

Updated

Nov 4, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 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.
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-mx3p-fhpw-x6rv.

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% 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.

Real-World Exposure

1 pkg affected

🐘tecnickcom/tcpdf

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

Description

TCPDF version <= 6.7.4 is vulnerable to ReDoS (Regular Expression Denial of Service) if parsing an untrusted HTML page with a crafted color.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`tecnickcom/tcpdf`	all versions	6.7.5`composer require tecnickcom/tcpdf:^6.7.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tecnickcom/tcpdf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tecnickcom/tcpdf to 6.7.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mx3p-fhpw-x6rv is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mx3p-fhpw-x6rv can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

TCPDF version <= 6.7.4 is vulnerable to ReDoS (Regular Expression Denial of Service) if parsing an untrusted HTML page with a crafted color.

O3 Security · Impact-Aware SCA

Is GHSA-mx3p-fhpw-x6rv in your dependencies?

O3 Security finds GHSA-mx3p-fhpw-x6rv across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works