GHSA-rj3r-r7hh-jxfq is a high-severity (CVSS 7.5) CWE-770 vulnerability in pdfmake. A fix is available for pdfmake — see the affected versions and patch details below.
pdfmake is vulnerable to Throttling via repeatedly redirecting URL in file embedding
Exploitation Status
No confirmed exploitation observed yet
- 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-rj3r-r7hh-jxfq.
EPSS Exploitation Probability
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-rj3r-r7hh-jxfq 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 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
pdfmakenpmDescription
Versions of the package pdfmake from 0.3.0-beta.1 and 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | pdfmake | ≥ 0.3.0-beta.1&&< 0.3.0-beta.17 | 0.3.0-beta.17npm install pdfmake@0.3.0-beta.17 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pdfmake, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rj3r-r7hh-jxfq can be triaged on real exposure rather than presence alone.
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
Is GHSA-rj3r-r7hh-jxfq in your dependencies?
O3 Security finds GHSA-rj3r-r7hh-jxfq across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.