How severe is GHSA-grhh-r4jj-8jh7?

No CVSS score has been assigned to GHSA-grhh-r4jj-8jh7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-grhh-r4jj-8jh7?

GHSA-grhh-r4jj-8jh7 affects the following packages: tecnickcom/tc-lib-pdf-font (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-grhh-r4jj-8jh7?

Update tecnickcom/tc-lib-pdf-font to 2.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-grhh-r4jj-8jh7 is resolved across your whole dependency graph.

How do I detect GHSA-grhh-r4jj-8jh7 in my Packagist dependencies?

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

How do I mitigate GHSA-grhh-r4jj-8jh7 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-grhh-r4jj-8jh7?

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

Is GHSA-grhh-r4jj-8jh7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-grhh-r4jj-8jh7 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-grhh-r4jj-8jh7?

GHSA-grhh-r4jj-8jh7 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 45th 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.

When was GHSA-grhh-r4jj-8jh7 published, and has it been updated?

GHSA-grhh-r4jj-8jh7 was published on December 27, 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-grhh-r4jj-8jh7 — tecnickcom/tc-lib-pdf-font

Fix: tecnickcom/TCPDF@a0a02ef

GHSA-grhh-r4jj-8jh7 is a security vulnerability in tecnickcom/tc-lib-pdf-font. A fix is available for tecnickcom/tc-lib-pdf-font — see the affected versions and patch details below.

tecnickcom/tc-lib-pdf-font mishandles fonts

Also known asCVE-2024-56520

Published

Dec 27, 2024

Updated

Nov 4, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 21, 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-grhh-r4jj-8jh7.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% 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/tc-lib-pdf-font

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

An issue was discovered in tc-lib-pdf-font before 2.6.4, as used in TCPDF before 6.8.0 and other products. Fonts are mishandled, e.g., FontBBox for Type 1 and TrueType fonts is misparsed.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`tecnickcom/tc-lib-pdf-font`	all versions	2.6.4`composer require tecnickcom/tc-lib-pdf-font:^2.6.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tecnickcom/tc-lib-pdf-font, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tecnickcom/tc-lib-pdf-font to 2.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-grhh-r4jj-8jh7 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-grhh-r4jj-8jh7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-grhh-r4jj-8jh7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in tc-lib-pdf-font before 2.6.4, as used in TCPDF before 6.8.0 and other products. Fonts are mishandled, e.g., FontBBox for Type 1 and TrueType fonts is misparsed.

O3 Security · Impact-Aware SCA

Is GHSA-grhh-r4jj-8jh7 in your dependencies?

O3 Security finds GHSA-grhh-r4jj-8jh7 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