How severe is GHSA-rj3r-r7hh-jxfq?

GHSA-rj3r-r7hh-jxfq has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rj3r-r7hh-jxfq?

GHSA-rj3r-r7hh-jxfq affects the following packages: pdfmake (npm). Ecosystems affected: npm.

How do I fix GHSA-rj3r-r7hh-jxfq?

Update pdfmake to 0.3.0-beta.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rj3r-r7hh-jxfq is resolved across your whole dependency graph.

How do I detect GHSA-rj3r-r7hh-jxfq in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pdfmake. 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.

How do I mitigate GHSA-rj3r-r7hh-jxfq 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-rj3r-r7hh-jxfq?

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

Is GHSA-rj3r-r7hh-jxfq actively exploited in the wild?

No public exploit code has been indexed for GHSA-rj3r-r7hh-jxfq 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-rj3r-r7hh-jxfq?

GHSA-rj3r-r7hh-jxfq has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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-rj3r-r7hh-jxfq published, and has it been updated?

GHSA-rj3r-r7hh-jxfq was published on October 7, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-rj3r-r7hh-jxfq: pdfmake (High 7.5)

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk24th percentile+0.26%

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.

Blast Radius

1 pkg affected

📦pdfmake

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

Description

Versions of the package pdfmake from 0.3.0-beta.1 to before 0.3.0-beta.17 are vulnerable to Allocation of Resources Without Limits or Throttling via repeatedly redirect URL in file embedding. An attacker can cause the application to crash or become unresponsive by providing crafted input that triggers this condition.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`pdfmake`	≥ 0.3.0-beta.1&&< 0.3.0-beta.17	0.3.0-beta.17

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pdfmake. 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.
Fix
Update pdfmake to 0.3.0-beta.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rj3r-r7hh-jxfq 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 pinpoints whether GHSA-rj3r-r7hh-jxfq 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-rj3r-r7hh-jxfq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of the package pdfmake from 0.3.0-beta.1 to before 0.3.0-beta.17 are vulnerable to Allocation of Resources Without Limits or Throttling via repeatedly redirect URL in file embedding. An attacker can cause the application to crash or become unresponsive by providing crafted input that triggers this condition.

O3 Security · Impact-Aware SCA

Is GHSA-rj3r-r7hh-jxfq in your dependencies?

O3 detects GHSA-rj3r-r7hh-jxfq across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-rj3r-r7hh-jxfq