PDF.js CVE-2026-16633
HIGHSeverity by source
Network-delivered PDF, no attacker privileges, user must open it (UI:R), JS executes in hosting origin (S:C), with full read/write access to that context.
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Arbitrary JavaScript execution in PDF.js (pdfjs-dist) allows an attacker to run unrestricted script in the context of any web application that renders attacker-controlled PDFs with default settings. The flaw stems from PDF.js's built-in scripting engine, which is enabled by default via the enableScripting flag, executing embedded JavaScript from PDFs without sandbox enforcement when no script-src CSP is present. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Two conditions must both be present: (1) enableScripting is set to true in the PDF.js configuration - this is the default value, so any application that has not explicitly set enableScripting: false is vulnerable; (2) the page hosting PDF.js does not enforce a Content Security Policy that blocks script-src, meaning either no CSP is present or the existing CSP permits inline scripts or unsafe-eval. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | No CVSS vector was provided by NVD or the advisory, so risk signals are inferred. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker crafts a PDF file containing embedded JavaScript that exfiltrates session cookies or performs actions on behalf of the victim by sending requests to the hosting application. The attacker distributes this PDF via phishing email, a malicious file upload feature, or a shared document link targeting an application that uses pdfjs-dist with default settings. … |
| Remediation | The primary fix is to upgrade pdfjs-dist to version 6.2.108 or later, as confirmed by the GHSA advisory at https://github.com/mozilla/pdf.js/security/advisories/GHSA-hq66-cqwq-w95j. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all applications using pdfjs-dist and identify which are running versions 5.6.83 through 6.2.107. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today
GHSA-hq66-cqwq-w95j