CVE-2026-16633 — pdfjs-dist
CVE-2026-16633 is a security vulnerability in pdfjs-dist. A fix is available for pdfjs-dist — see the affected versions and patch details below.
PDF.js: Arbitrary JavaScript execution upon opening a malicious PDF
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.
pdfjs-distnpmDescription
Impact
If PDF.js is used to load a malicious PDF, and PDF.js is configured with enableScripting set to true (which is the default value) and no CSP for disallowing script-src, unrestricted attacker-controlled JavaScript will be executed in the context of the hosting domain.
Patches
Workarounds
Set enableScripting to false or set a CSP.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | pdfjs-dist | ≥ 5.6.83&&< 6.2.108 | 6.2.108npm install pdfjs-dist@6.2.108 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pdfjs-dist, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pdfjs-dist to 6.2.108 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-16633 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-16633 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-16633. 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-16633 in your dependencies?
O3 Security finds CVE-2026-16633 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.