LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24737: jsPDF has a PDF Injection in AcroFormChoiceField which allows Arbitrary JavaScript Execution

jsPDF is a library to generate PDFs in JavaScript. Prior to 4.1.0, user control of properties and methods of the Acroform module allows users to inject arbitrary PDF objects, such as JavaScript actions. If given the possibility to pass unsanitized input to one of the following methods or properties, a user can inject arbitrary PDF objects, such as JavaScript actions, which are executed when the victim opens the document. The vulnerable API members are AcroformChoiceField.addOption, AcroformChoiceField.setOptions, AcroFormCheckBox.appearanceState, and AcroFormRadioButton.appearanceState. The vulnerability has been fixed in jsPDF@4.1.0.

HighCVSS 8.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24737 affects jsPDF before 4.1.0. If an application lets untrusted users influence certain PDF form fields, they may inject PDF objects, including JavaScript actions, into generated documents. The harmful content runs when a victim opens the PDF, so business risk depends on where jsPDF-generated PDFs are created, shared, and trusted.

Executive priority

Prioritize remediation where jsPDF-generated PDFs are trusted, externally influenced, or opened by employees or customers. This is high severity because successful abuse can affect confidentiality and integrity after a victim opens a document, but the provided sources do not confirm active exploitation.

Technical view

The issue is PDF injection in jsPDF AcroForm APIs: AcroformChoiceField.addOption, AcroformChoiceField.setOptions, AcroFormCheckBox.appearanceState, and AcroFormRadioButton.appearanceState. Unsanitized input can alter PDF structure and add JavaScript actions. jsPDF versions before 4.1.0 are affected; 4.1.0 contains the fix. CVSS 3.1 is 8.3 high.

Likely exposure

Applications using parallax/jsPDF below 4.1.0 are exposed when untrusted input reaches the named AcroForm methods or properties. Exposure is higher for customer portals, document workflows, or automated PDF generation where generated PDFs are opened by staff, customers, or downstream partners.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires attacker-controlled input reaching vulnerable jsPDF AcroForm members and a victim opening the generated PDF in an environment that executes embedded PDF JavaScript.

Researcher notes

Focus assessment on data flow into the named AcroForm APIs, not every jsPDF use. Viewer behavior matters because the JavaScript action executes on document open. Evidence is strong for affected versions and fixed version, but the bundle does not provide exploit-in-the-wild evidence.

Mitigation direction

  • Upgrade jsPDF to version 4.1.0 or later.
  • Inventory applications and packages using parallax/jsPDF below 4.1.0.
  • Block untrusted input from the affected AcroForm APIs until upgraded.
  • Review vendor advisories and Red Hat errata for distribution-specific guidance.
  • Treat generated PDFs from affected workflows as potentially unsafe until remediated.

Validation and detection

  • Check dependency manifests and lockfiles for jsPDF versions below 4.1.0.
  • Search code for the four affected AcroForm members named in the advisory.
  • Trace whether user-controlled data can reach those members.
  • Confirm deployed builds contain jsPDF 4.1.0 or later.
  • Review PDF-generation workflows that share documents with internal or external users.
Prepared
Confidence
high
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cwe · low confidence lookup

CWE-917: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2026-24737 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.3 (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:L

Official CVE source material

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.

2CVSS vectors
5Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L2.85.5redhat-SADP
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N2.85.2GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

8.3High
CVSS 3.1 vector shape for CVE-2026-24737Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPjsPDF: jsPDF: Arbitrary code execution via unsanitized input in Acroform module
other:Red Hat severity ratingcvssV3_1
  • 2026-02-03T00:01:51.004Z: Reported to Red Hat.
  • 2026-02-02T20:29:05.011Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
parallaxjsPDF< 4.1.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-116 · source CWE mapping

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.

CWE-917 · source CWE mapping

Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')

Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.