How severe is CVE-2026-22787?

No CVSS score has been assigned to CVE-2026-22787 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-22787?

CVE-2026-22787 affects the following packages: html2pdf.js (npm). Ecosystems affected: npm.

How do I fix CVE-2026-22787?

Update html2pdf.js to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22787 is resolved across your whole dependency graph.

How do I detect CVE-2026-22787 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for html2pdf.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-22787 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2026-22787 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-22787 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-22787?

CVE-2026-22787 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-22787?

CVE-2026-22787 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-22787 published, and has it been updated?

CVE-2026-22787 was published on January 14, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-22787 — html2pdf.js

Fix: eKoopmans/html2pdf.js@988826e

CVE-2026-22787 is a Cross-site Scripting (XSS) vulnerability in html2pdf.js. A fix is available for html2pdf.js — see the affected versions and patch details below.

html2pdf.js has a cross-site scripting vulnerability

Also known asGHSA-w8x4-x68c-m6fc

Published

Jan 14, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22787.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

268other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

html2pdf.jsnpm

1.6Mdownloads / week

Description

Impact

html2pdf.js contains a cross-site scripting (XSS) vulnerability when given a text source rather than an element. This text is not sufficiently sanitized before being attached to the DOM, allowing malicious scripts to be run on the client browser and risking the confidentiality, integrity, and availability of the page's data.

Example attack vector:

import html2pdf from 'html2pdf.js/src/index.js';

const maliciousHTML = '<img src=x onerror="alert(document.cookie)">';
html2pdf(maliciousHTML);
// or html2pdf().from(maliciousHTML);

Patches

This vulnerability has been fixed in [email protected] to sanitize text sources using DOMPurify. There are no other breaking changes in this version.

Workarounds

Users of earlier versions of html2pdf.js must safely sanitize any text before using it as a source in html2pdf.js.

References

Initial report: https://github.com/eKoopmans/html2pdf.js/issues/865
Fix: https://github.com/eKoopmans/html2pdf.js/pull/877, v0.14.0
CVE-2026-22787: https://nvd.nist.gov/vuln/detail/CVE-2026-22787

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`html2pdf.js`	all versions	0.14.0`npm install html2pdf.js@0.14.0`

Affected Products

1 product · 1 configurations

Application

html2pdf.jsekoopmans

< 0.14.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for html2pdf.js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update html2pdf.js to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22787 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact html2pdf.js contains a cross-site scripting (XSS) vulnerability when given a text source rather than an element. This text is not sufficiently sanitized before being attached to the DOM, allowing malicious scripts to be run on the client browser and risking the confidentiality, integrity, and availability of the page's data. Example attack vector: ```js import html2pdf from 'html2pdf.js/src/index.js'; const maliciousHTML = '<img src=x onerror="alert(document.cookie)">'; html2pdf(maliciousHTML); // or html2pdf().from(maliciousHTML); ``` ### Patches This vulnerability has been fix

O3 Security · Impact-Aware SCA

Is CVE-2026-22787 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works