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

CVE-2020-28469

HIGH

CVE-2020-28469 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in glob-parent. 3 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2020-28469 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

glob-parent vulnerable to Regular Expression Denial of Service in enclosure regex

Also known asBIT-gulp-2020-28469GHSA-ww39-953v-wcq6
Published
Jun 3, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
3 known

Blast Radius

1 pkg affected
📦glob-parent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmglob-parent4.0.0&&< 5.1.25.1.2
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for glob-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update glob-parent to 5.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-28469 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2020-28469 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-28469. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This affects the package glob-parent before 5.1.2. The enclosure regex used to check for strings ending in enclosure containing path separator.
O3 Security · Impact-Aware SCA

Is CVE-2020-28469 in your dependencies?

O3 detects CVE-2020-28469 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.