# CVE-2026-25535: jsPDF Affected by Client-Side/Server-Side Denial of Service via Malicious GIF Dimensions

> Attackers can cause denial of service in applications using jsPDF by providing malicious GIF files with excessive dimensions to the addImage method.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2026
- **Updated:** 7 Sep 2026
- **Also known as:** GHSA-67pg-wm7f-q7fj, ROOT-APP-NPM-CVE-2026-25535

## What is CVE-2026-25535?

CVE-2026-25535 is a high-severity denial of service vulnerability in parallax jsPDF, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

jsPDF is a library to generate PDFs in JavaScript. Prior to 4.2.0, user control of the first argument of the `addImage` method results in denial of service. If given the possibility to pass unsanitized image data or URLs to the `addImage` method, a user can provide a harmful GIF file that results in out of memory errors and denial of service. Harmful GIF files have large width and/or height entries in their headers, which lead to excessive memory allocation. Other affected methods are: `html`. The vulnerability has been fixed in jsPDF 4.2.0. As a workaround, sanitize image data or URLs before passing it to the addImage method or one of the other affected methods.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-25535?

2 open source packages ship an affected version, including jspdf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jspdf` | npm | All versions | 4.2.0 |
| `jspdf` | npm | All versions | 4.2.0 |

Products: Parall Jspdf.

## How do I fix CVE-2026-25535?

Upgrade jspdf to 4.2.0 or later.

## Is CVE-2026-25535 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25535 exists.

## Other vulnerabilities in parallax jsPDF

- [CVE-2026-31938](https://insights.sbomify.com/CVE-2026-31938/): jsPDF has HTML Injection in New Window paths (critical 9.6)
- [CVE-2025-68428](https://insights.sbomify.com/CVE-2025-68428/): jsPDF has Local File Inclusion/Path Traversal vulnerability (critical 9.2)
- [CVE-2026-24133](https://insights.sbomify.com/CVE-2026-24133/): jsPDF Affected by Denial of Service (DoS) via Unvalidated BMP Dimensions in BMPDecoder (high 8.7)
- [CVE-2025-57810](https://insights.sbomify.com/CVE-2025-57810/): jsPDF Parsing of Corrupt PNGs Leads to Potential Denial of Service (DoS) (high 8.7)
- [CVE-2025-29907](https://insights.sbomify.com/CVE-2025-29907/): jsPDF Bypass Regular Expression Denial of Service (ReDoS) (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25535 and fix it if it is affected.

What it is: CVE-2026-25535 is a high-severity denial of service vulnerability in parallax jsPDF, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25535 exists.

Affected packages and fixed versions:
- jspdf (npm): affected all versions; fixed in 4.2.0
- jspdf (npm): affected all versions; fixed in 4.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25535/ (Markdown: https://insights.sbomify.com/CVE-2026-25535/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25535
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25535
- OSV: https://osv.dev/vulnerability/CVE-2026-25535

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25535/
Summaries are generated and may contain mistakes; the official description above is the record.