NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

thlorenz browserify-shim vulnerable to prototype pollutionGHSA-866w-wm4h-95c6

CRITICALFix: thlorenz/browserify-shim#246

GHSA-866w-wm4h-95c6 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in browserify-shim. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for browserify-shim — see the affected versions and patch details below.

Also known asCVE-2022-37617
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.00%0.68%1.36%2.04%0.5%1.5%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

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.

304other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
browserify-shimnpm
37Kdownloads / week

Description

Prototype pollution vulnerability in function resolveShims in resolve-shims.js in thlorenz browserify-shim 3.8.15 via the k variable in resolve-shims.js.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmbrowserify-shimall versions3.8.16npm install browserify-shim@3.8.16

Affected Products

1 product · 1 configurations
Application
browserify-shimbrowserify-shim_project
1 version
3.8.15
Exploits & PoCs
2

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 browserify-shim, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update browserify-shim to 3.8.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-866w-wm4h-95c6 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

Prototype pollution vulnerability in function `resolveShims` in resolve-shims.js in thlorenz browserify-shim 3.8.15 via the `k` variable in resolve-shims.js.
O3 Security · Impact-Aware SCA

Is GHSA-866w-wm4h-95c6 in your dependencies?

Find it across npm, including transitive dependencies.

GHSA-866w-wm4h-95c6: browserify-shim — Fixed in 3.8.16