cve.bz

CVE-2026-26801 pdfmake pdfmake: SSRF

7.5 highExploit referenceEPSS 0.5%Fix available

High (7.5) in pdfmake pdfmake. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in pdfmake 0.3.6.

On this page
Server-Side Request Forgery (SSRF) vulnerability in pdfmake versions 0.3.0-beta.2 through 0.3.5 allows a remote attacker to obtain sensitive information via the src/URLResolver.js component. The fix was released in version 0.3.6 which introduces the setUrlAccessPolicy() method allowing server operators to define URL access rules. A warning is now logged when pdfmake is used server-side without a policy configured.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-03-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-26801 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-26801?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-26801?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-26801 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
pdfmake:pdfmakefrom 0.3.1 through 0.3.5
pdfmake:pdfmake0.3.0
pdfmake:pdfmake0.3.0:beta10
pdfmake:pdfmake0.3.0:beta11
pdfmake:pdfmake0.3.0:beta12
pdfmake:pdfmake0.3.0:beta13
pdfmake:pdfmake0.3.0:beta14
pdfmake:pdfmake0.3.0:beta15
pdfmake:pdfmake0.3.0:beta16
pdfmake:pdfmake0.3.0:beta17
pdfmake:pdfmake0.3.0:beta18
pdfmake:pdfmake0.3.0:beta19
pdfmake:pdfmake0.3.0:beta2
pdfmake:pdfmake0.3.0:beta3
pdfmake:pdfmake0.3.0:beta4
pdfmake:pdfmake0.3.0:beta5
pdfmake:pdfmake0.3.0:beta6
pdfmake:pdfmake0.3.0:beta7
pdfmake:pdfmake0.3.0:beta8
pdfmake:pdfmake0.3.0:beta9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wp52-r2fp-4vmrnpmpdfmake>=0.3.0-beta.2 <0.3.60.3.6

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • mariopepe/CVE-2026-26801-pdfmake-ssrf Harbor Check: matches CVE 0 stars, JavaScript, created
    PoC for CVE-2026-26801: SSRF in pdfmake URLResolver.js (>= 0.3.0-beta.2, <= 0.3.5)

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON