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
Responses served through protocol.registerFileProtocol or protocol.registerHttpProtocol for a custom scheme registered with supportFetchAPI: true but without corsEnabled: true could be read cross-origin by web content. This completes the fix for CVE-2026-70604.
Apps are only affected if they register such a scheme, serve it through one of those handlers, and load untrusted content. Apps that set corsEnabled: true, or that do not load untrusted content, are not affected.
Set corsEnabled: true on the scheme, or do not load untrusted content in windows that can reach it.
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.21%
estimated chance of real-world exploitation in the next 30 days, higher than 11.8% 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.