CVE-2026-22787 — html2pdf.js
Fix: eKoopmans/html2pdf.js@988826eCVE-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
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
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.
html2pdf.jsnpmDescription
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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | html2pdf.js | all versions | 0.14.0npm install html2pdf.js@0.14.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-22787 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-22787. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-22787 in your dependencies?
O3 Security finds CVE-2026-22787 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.