pdfmake is vulnerable to Throttling via repeatedly redirecting URL in file embeddingGHSA-rj3r-r7hh-jxfq
HIGHFix: bpampuch/pdfmake@7411696GHSA-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.
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
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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 |
Affected Products
pdfmakepdfmakeDetection & 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
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-rj3r-r7hh-jxfq in your dependencies?
Find it across npm, including transitive dependencies.