Security readout for executives and security teams
Plain-English summary
Applications using vulnerable jsPDF versions may let an attacker turn an unsanitized annotation color into malicious PDF content, including JavaScript actions. The action might run when a recipient opens or interacts with the generated PDF. This creates serious confidentiality and integrity risk, but requires a vulnerable application flow and user interaction.
Executive priority
Treat as a prompt remediation item for systems generating PDFs from external input. Prioritize confirmation of reachable createAnnotation flows, then upgrade to 4.2.1 or later. Urgency is high because potential impacts are severe, although the available sources do not establish active exploitation or universal exposure.
Technical view
Before jsPDF 4.2.1, createAnnotation does not safely neutralize attacker-controlled color input, permitting arbitrary PDF object injection. The advisory identifies JavaScript actions as one possible injected object. CVSS 3.1 scores it 8.1: network-reachable, low complexity, no privileges required, user interaction required, with high confidentiality and integrity impact.
Likely exposure
Exposure exists where jsPDF earlier than 4.2.1 is deployed and untrusted data can reach createAnnotation's color parameter without effective sanitization. Internet-facing PDF-generation workflows and applications producing PDFs later opened by employees, customers, or partners deserve priority. Merely having jsPDF installed does not establish an exploitable path.
Exploitation context
The supplied record does not identify known active exploitation, and the CVE is not listed as KEV. Exploitation requires attacker control over the relevant input and a recipient opening or interacting with the resulting PDF. Whether an injected action triggers may depend on the PDF viewer and its security settings.
Researcher notes
The issue maps to CWE-116 and CWE-94 and concerns PDF syntax/object injection through the FreeText annotation color value. Review the linked vulnerable code and fixing commit when assessing custom forks or backports. Validate data flow and output structure without assuming every jsPDF installation calls the affected API or every viewer executes injected actions.
Mitigation direction
- Upgrade jsPDF to version 4.2.1 or later.
- Sanitize untrusted values before passing them to createAnnotation.
- Restrict annotation color inputs to an explicit, validated format.
- Prioritize services that generate PDFs from unauthenticated or externally supplied data.
- Consult the jsPDF advisory and release notes before deploying the update.
Validation and detection
- Inventory direct and transitive jsPDF versions across build and deployment artifacts.
- Search application code for createAnnotation calls and trace the color argument's origin.
- Confirm untrusted input cannot reach the color parameter without strict validation.
- Verify production artifacts resolve jsPDF 4.2.1 or later.
- Run regression tests confirming rejected inputs cannot alter generated PDF object structure.
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-31898 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
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
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:U/C:H/I:H/A:N2.85.2GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2redhat-SADPVulnerability scoring details
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
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-03-18T04:02:12.103Z: Reported to Red Hat.
- 2026-03-18T03:03:43.469Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/parallax/jsPDF/security/advisories/GHSA-7x6v-j9x4-qf24CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/parallax/jsPDF/commit/4155c4819d5eca284168e51e0e1e81126b4f14b8CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/parallax/jsPDF/blob/b1607a9391d4cd65ea7ade25998aea8345ae1be3/src/modules/annotations.js#L193-L208CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/parallax/jsPDF/releases/tag/v4.2.1CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-31898CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2448547CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-31898.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.