CVE-2025-11362: Versions of the package pdfmake from 0.3.0-beta.1 and before 0.3.0-beta.17 are vulnerable to Allocation of...
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.
Security readout for executives and security teams
Plain-English summary
Affected pdfmake beta versions can be forced to consume resources while following repeated redirects for an embedded file. In applications accepting attacker-controlled document input, this may crash or freeze PDF generation, disrupting dependent services. The reported impact is availability loss, not data theft or modification.
Executive priority
Prioritize remediation for internet-facing or multi-tenant PDF services that accept untrusted document content. A successful attack could interrupt document generation or exhaust shared capacity without authentication. Internal systems processing only trusted templates can follow normal high-severity patching timelines after confirming their input boundaries.
Technical view
CVE-2025-11362 is a CWE-770 resource-allocation flaw affecting pdfmake versions from 0.3.0-beta.1 through versions before 0.3.0-beta.17, including its npm WebJar packaging. Repeated URL redirects during file embedding can exhaust resources. CVSS 4.0 rates it 8.7, with network reachability, low complexity, no privileges or interaction, and high availability impact.
Likely exposure
Exposure is most likely where affected pdfmake code processes documents containing attacker-controlled remote file URLs. Risk is lower if remote embedding is disabled, input is trusted, or the vulnerable beta range is absent. Both direct npm dependencies and org.webjars.npm:pdfmake should be inventoried.
Exploitation context
The supplied record does not identify known active exploitation, and the CVE is not listed as KEV in the bundle. The CVSS vector indicates a remotely triggerable, unauthenticated condition, but practical reachability depends on whether an application lets untrusted input influence embedded-file URLs.
Researcher notes
The evidence supports uncontrolled resource allocation during redirect handling and availability-only impact. The referenced upstream commit indicates a code-level correction, while the stated affected range places 0.3.0-beta.17 outside vulnerability scope. The bundle provides no exploit observations, deployment prevalence, or proof that every application using the package exposes the vulnerable path.
Mitigation direction
Upgrade pdfmake to 0.3.0-beta.17 or a later vendor-supported release.
Update org.webjars.npm:pdfmake where the affected beta range is packaged.
Temporarily disable untrusted remote file embedding when immediate upgrading is impossible.
Apply resource limits and availability monitoring around PDF-generation services as defense in depth.
Validation and detection
Inspect manifests and lockfiles for pdfmake versions from 0.3.0-beta.1 through 0.3.0-beta.16.
Check Java dependencies for affected org.webjars.npm:pdfmake packaging.
Trace whether untrusted document data can control remote embedded-file URLs.
Confirm production artifacts contain the upgraded version, not only updated manifests.
Review service telemetry for redirect loops, resource exhaustion, crashes, or prolonged PDF jobs.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.