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

Applications using jsPDF before 4.1.0 may create weaponized PDFs when untrusted data reaches certain form-field settings. Injected JavaScript actions can execute when a recipient opens the generated document, potentially exposing data, altering information, or disrupting the viewer. Opening the PDF is required.

Executive priority

Prioritize remediation for internet-facing or externally influenced PDF-generation workflows. Upgrade promptly where recipients routinely open generated PDFs or sensitive data is accessible. Lower urgency may be justified only after confirming the affected APIs are unused or cannot receive untrusted input.

Technical view

CVE-2026-24737 is PDF syntax injection in four AcroForm APIs: ChoiceField.addOption, ChoiceField.setOptions, CheckBox.appearanceState, and RadioButton.appearanceState. Unsanitized attacker-controlled values can introduce arbitrary PDF objects, including JavaScript actions. Versions before 4.1.0 are affected; 4.1.0 contains the fix. CVSS 3.1 is 8.3.

Likely exposure

Exposure requires jsPDF below 4.1.0 and a data flow allowing untrusted input into at least one vulnerable AcroForm member. Risk is greatest for public or unauthenticated PDF-generation services whose documents are opened by customers, employees, or partners. Merely installing jsPDF does not prove exploitability.

Exploitation context

The supplied sources do not establish active exploitation, and the CVE is not identified as KEV. Exploitation nevertheless has low stated complexity and requires a victim to open the generated PDF. Actual behavior may depend on the PDF viewer and its JavaScript security controls.

Researcher notes

The key validation question is whether attacker-controlled strings cross a PDF-object serialization boundary through the named APIs. CWE-116 and CWE-917 are assigned. The source bundle identifies confidentiality and integrity as the largest impacts, but provides no confirmed exploitation evidence or detailed PDF-viewer compatibility findings.

Mitigation direction

  • Upgrade jsPDF to version 4.1.0 or later.
  • Prevent untrusted input from reaching the four vulnerable AcroForm members until upgraded.
  • Regenerate externally distributed PDFs if potentially hostile input may have influenced affected fields.
  • Consult downstream vendor advisories when jsPDF is supplied through a packaged product.

Validation and detection

  • Confirm deployed and bundled jsPDF versions, including transitive dependencies, are 4.1.0 or later.
  • Search application code for all four affected API members.
  • Trace each affected value to determine whether users or external systems can control it.
  • Verify production artifacts use the remediated dependency, not only updated manifests.
  • Inspect representative generated PDFs using safe analysis procedures for unexpected actions or objects.
Prepared
Confidence
high
Sources
5

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.