Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

ngx-extended-pdf-viewer bundles a version of pdf.js vulnerable to CVE-2026-16633GHSA-w9hm-4m3m-fxmm

GHSA-w9hm-4m3m-fxmm is a security vulnerability in ngx-extended-pdf-viewer. A fix is available for ngx-extended-pdf-viewer — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 6, 2026 · OSV.dev, 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.

32other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
ngx-extended-pdf-viewernpm
256Kdownloads / week

Description

ngx-extended-pdf-viewer embeds a fork of Mozilla's pdf.js rather than depending on pdfjs-dist, so this vulnerability is not visible to dependency scanners through package.json.

Impact

Opening a malicious PDF can execute attacker-controlled JavaScript in the context of the hosting page. Upstream advisory: GHSA-hq66-cqwq-w95j / CVE-2026-16633.

Exposure.

The sandbox half of the issue requires enableScripting, which pdf.js enables by default but this library does not — so the default configuration was less exposed than upstream's. The other half concerns XFA rich text and is reachable whenever enableXfa is true, which is the default here. Do not assume the default configuration was safe.

Patches

29.0.0-rc.3 cherry-picks Mozilla's fix (pdf.js 6.2.108) into both the stable and bleeding-edge engines. Only the latest release receives security updates.

Workarounds

Set pdfDefaultOptions.enableXfa = false if you do not need XFA forms, and/or apply a CSP disallowing inline script-src.

Verifying.

From 29.0.0 the package ships sbom.json and vex.json. The SBOM records the applied fix as a CycloneDX pedigree.patches entry; the VEX carries a resolved_with_pedigree statement so scanners stop flagging the engine's nominal version.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmngx-extended-pdf-viewer≥ 27.0.0-rc.0&&< 29.0.0-rc.329.0.0-rc.3npm install ngx-extended-pdf-viewer@29.0.0-rc.3

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update ngx-extended-pdf-viewer to 29.0.0-rc.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9hm-4m3m-fxmm is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

ngx-extended-pdf-viewer embeds a fork of Mozilla's pdf.js rather than depending on pdfjs-dist, so this vulnerability is not visible to dependency scanners through package.json. ### Impact Opening a malicious PDF can execute attacker-controlled JavaScript in the context of the hosting page. Upstream advisory: GHSA-hq66-cqwq-w95j / CVE-2026-16633. ### Exposure. The sandbox half of the issue requires enableScripting, which pdf.js enables by default but this library does not — so the default configuration was less exposed than upstream's. The other half concerns XFA rich text and is reachable w
O3 Security · Impact-Aware SCA

Is GHSA-w9hm-4m3m-fxmm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
ngx-extended-pdf-viewer bundles a version of pdf.js…