How severe is CVE-2020-15262?

CVE-2020-15262 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-15262?

CVE-2020-15262 affects the following packages: webpack-subresource-integrity (npm). Ecosystems affected: npm.

How do I fix CVE-2020-15262?

Update webpack-subresource-integrity to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-15262 is resolved across your whole dependency graph.

How do I detect CVE-2020-15262 in my npm dependencies?

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

How do I mitigate CVE-2020-15262 if there is no patch (or I can't update yet)?

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.

Is CVE-2020-15262 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-15262 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-15262?

CVE-2020-15262 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-15262?

CVE-2020-15262 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-15262 published, and has it been updated?

CVE-2020-15262 was published on October 19, 2020 and was last updated on July 9, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

LOW severity

CVE-2020-15262 — webpack-subresource-integ…

LOWFix: waysact/webpack-subresource-integrity@3d7090c

CVE-2020-15262 is a low-severity (CVSS 3.7) CWE-345 vulnerability in webpack-subresource-integrity. A fix is available for webpack-subresource-integrity — see the affected versions and patch details below.

Unprotected dynamically loaded chunks

Also known asGHSA-4fc4-chg7-h8gh

Published

Oct 19, 2020

Updated

Jul 9, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2020-15262 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

111other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

webpack-subresource-integritynpm

4.9Mdownloads / week

Description

Impact

All dynamically loaded chunks receive an invalid integrity hash that is ignored by the browser, and therefore the browser cannot validate their integrity. This removes the additional level of protection offered by SRI for such chunks. Top-level chunks are unaffected.

Patches

This issue is patched in version 1.5.1.

Workarounds

N/A

References

https://github.com/waysact/webpack-subresource-integrity/issues/131

For more information

If you have any questions or comments about this advisory:

Comment on webpack-subresource-integrity issue #131
Or email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`webpack-subresource-integrity`	all versions	1.5.1`npm install webpack-subresource-integrity@1.5.1`

Affected Products

1 product · 1 configurations

Application

webpack-subresource-integritywebpack-subresource-integrity_project

< 1.5.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for webpack-subresource-integrity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update webpack-subresource-integrity to 1.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-15262 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.

Frequently Asked Questions

### Impact All dynamically loaded chunks receive an invalid integrity hash that is ignored by the browser, and therefore the browser cannot validate their integrity. This removes the additional level of protection offered by SRI for such chunks. Top-level chunks are unaffected. ### Patches This issue is patched in version 1.5.1. ### Workarounds N/A ### References https://github.com/waysact/webpack-subresource-integrity/issues/131 ### For more information If you have any questions or comments about this advisory: * Comment on [webpack-subresource-integrity issue #131](https://github.com