Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: < 41.10.6
Patched in 41.10.6
Vulnerable: >= 42.0.0-alpha.1, < 42.9.2
Patched in 42.9.2
Vulnerable: >= 43.0.0-alpha.1, < 43.4.1
Patched in 43.4.1
Vulnerable: >= 44.0.0-alpha.1, < 44.0.0-beta.5
Patched in 44.0.0-beta.5
Details
Windows opened from a sandboxed top-level document did not inherit that document's HTML sandbox restrictions, so content that was meant to run sandboxed could open a window with the app's full origin. GHSA-hq2x-r82h-9wj4 covers the same issue for sandboxed iframes.
Apps are only affected if they render untrusted content in a sandboxed top-level document that allows popups. Apps that deny popups from untrusted content with setWindowOpenHandler are not affected.
Return { action: 'deny' } from setWindowOpenHandler for windows opened by untrusted content.
44.0.0-beta.543.4.142.9.241.10.6If you have any questions or comments about this advisory, email us at [email protected]
EPSS, exploit probability
Low0.24%
estimated chance of real-world exploitation in the next 30 days, higher than 14.7% of every CVE FIRST.org scores
Refreshed 11/14/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
More npm advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.