Security readout for executives and security teams
Plain-English summary
Applications using jsPDF before 4.2.0 may create dangerous PDFs when untrusted data reaches the addJS method. An attacker could alter the PDF’s internal structure or cause malicious actions when a recipient opens it. Risk depends on whether the application exposes that specific data path.
Executive priority
Treat internet-facing or multi-user PDF-generation systems using addJS with untrusted input as urgent. Patch promptly and prioritize data-flow confirmation. Systems that do not call addJS are lower priority, but dependency inventory is still necessary because the supplied severity reflects potentially broad impact.
Technical view
The addJS method failed to safely encode its argument within a PDF JavaScript string. Attacker-controlled input could escape the intended delimiter and inject arbitrary PDF objects. The issue is classified under improper output encoding and code injection, with CVSS 3.1 score 9.6. Version 4.2.0 contains the fix.
Likely exposure
Exposure is likely where jsPDF versions below 4.2.0 generate documents using addJS with user-controlled or externally sourced input. Merely having jsPDF installed does not establish exploitability; applications must confirm the vulnerable method and data flow are present.
Exploitation context
Exploitation is remotely initiable and low complexity according to the supplied CVSS vector, but requires a user to open the generated PDF. The bundle does not identify CISA KEV listing or provide evidence of active exploitation. Potential consequences include document manipulation and confidentiality, integrity, or availability impacts.
Researcher notes
The decisive exposure condition is attacker influence over the addJS argument in jsPDF before 4.2.0. Review direct and transitive dependency resolution plus shipped bundles, since manifests alone may not represent production. The supplied sources identify the fixing commit and release; no active-exploitation claim is supported.
Mitigation direction
- Upgrade jsPDF to version 4.2.0 or later.
- Rebuild and redeploy every application or service bundling the affected dependency.
- If upgrading is delayed, escape parentheses in user-provided JavaScript before passing it to addJS.
- Restrict untrusted input from reaching addJS until remediation is verified.
Validation and detection
- Inventory direct, transitive, bundled, and client-side copies of jsPDF.
- Confirm production artifacts resolve jsPDF to version 4.2.0 or later.
- Search application code for addJS calls and trace each input source.
- Verify untrusted data cannot reach addJS without the documented escaping.
- Run controlled regression tests confirming generated PDFs remain structurally valid after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-116: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
Open ATT&CK lookupCVE-2026-25755 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86redhat-SADPCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-19T15:01:21.761Z: Reported to Red Hat.
- 2026-02-19T14:41:46.941Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/parallax/jsPDF/security/advisories/GHSA-9vjf-qc39-jprpCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/parallax/jsPDF/commit/56b46d45b052346f5995b005a34af5dcdddd5437CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/ZeroXJacks/CVEs/blob/main/2026/CVE-2026-25755.mdCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/parallax/jsPDF/releases/tag/v4.2.0CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-25755CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2440993CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25755.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:7110CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/errata/RHSA-2026:7128CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Encoding or Escaping of Output
Improper Encoding or Escaping of Output represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.