Skip to content

← Public intelligence

npm package

pdfmake

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5npmAmendedPublished

    pdfmake is vulnerable to server-side request forgery (SSRF)

    CVE-2026-26801 · GHSA-wp52-r2fp-4vmr

    Affected
    • npm pdfmake >= 0.3.0-beta.2, < 0.3.6
    Fixed in
    0.3.6· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 0.3.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.7npmAmendedPublished

    pdfmake is vulnerable to Throttling via repeatedly redirecting URL in file embedding

    CVE-2025-11362 · GHSA-rj3r-r7hh-jxfq

    Affected
    • npm pdfmake >= 0.3.0-beta.1, < 0.3.0-beta.17
    Fixed in
    0.3.0-beta.17· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 0.3.0-beta.17 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →