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

Published Feb 19, 2026
·
Updated

Impact

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, wich lead to excessive memory allocation.

Other affected methods are: html.

Example attack vector:

js import { jsPDF } from "jspdf"

// malicious GIF image data with large width/height headers const payload = ...

const doc = new jsPDF();

doc.addImage(payload, "GIF", 0, 0, 100, 100);

Patches

The vulnerability has been fixed in jsPDF 4.1.1. Upgrade to jspdf@>=4.2.0.

Workarounds

Sanitize image data or URLs before passing it to the addImage method or one of the other affected methods. References https://github.com/ZeroXJacks/CVEs/blob/main/2026/CVE-2026-25535.md

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
npm/jspdf<4.2.0
npm/jspdf<4.2.0
4.2.0
parall jspdf Node.js<4.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/jspdf to a version that resolves this vulnerability.

    Fixed in 4.2.0
  2. Upgrade

    Upgrade jspdf to a version that resolves this vulnerability.

    Fixed in 4.2.0
  3. Configuration

    Before calling jsPDF addImage(payload, "GIF", x, y, w, h) (and other affected methods, listed as `html`), sanitize the image data or URLs so that harmful GIFs with large width/height header values cannot be passed as unsanitized first arguments.

    jsPDF Sanitize image data or URLs passed to addImage (and other affected methods) = enabled

Event History

Feb 19, 2026
CVE Published
via MITRE·02:34 PM
Data Sourced
via MITRE·02:34 PM
DescriptionWeakness
Data Sourced
via Red Hat·03:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·03:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·03:25 PM
Data Sourced
via GitHub·03:25 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-25535?

The severity of CVE-2026-25535 is classified as a denial of service vulnerability.

2

How do I fix CVE-2026-25535?

To fix CVE-2026-25535, update to a version of jsPDF that is 4.2.0 or later.

3

What software is affected by CVE-2026-25535?

CVE-2026-25535 affects versions of jsPDF up to 4.2.0.

4

What is the potential impact of CVE-2026-25535?

The potential impact of CVE-2026-25535 is user-controlled denial of service via the `addImage` method.

5

Can untrusted users exploit CVE-2026-25535?

Yes, untrusted users can exploit CVE-2026-25535 by passing unsanitized image data to the `addImage` method.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203