Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighPublic exploit

PDF object injection in jsPDF addJS (CVE-2026-25755)

IdentifiersCVE-2026-25755CWE-74

jsPDF (prior to 4.2.0) is vulnerable to PDF object injection via the addJS method. The addJS implementation concatenates user-controlled input directly into a PDF /JS string (e.g., this.internal.out("/JS (" + text + ")")) without properly escaping PDF string delimiters (notably the closing parenthesis). An attacker who can control the addJS argument can craft input that terminates the intended /JS literal and injects arbitrary PDF objects/structures (e.g., actions such as /OpenAction or other object graph modifications) into the generated document, affecting users who open the produced PDF.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker can embed arbitrary PDF objects and actions into generated PDFs, enabling malicious behavior on document open (e.g., injected actions like /OpenAction) and/or manipulation of document structure (annotations, signatures/metadata, appearance changes, phishing content). The impact is on downstream consumers of the generated PDF (victims opening the file) and may vary by PDF viewer parsing/behavior.

Mitigation

If you can’t patch tonight, do this now.

Do not pass untrusted/user-controlled input to addJS. If addJS must be used with user-provided content, escape PDF string metacharacters—specifically parentheses (and per PDF string rules, also backslashes)—before passing the value to addJS, and apply strict input validation/allowlisting for any embedded script content.

Remediation

Patch, then assume compromise.

Upgrade jsPDF/jspdf to 4.2.0 or later, where the issue is fixed by properly sanitizing/escaping the addJS content before emitting it into the PDF output.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ParallJspdfapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.