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

CVE-2022-37264 — steal

CRITICAL

CVE-2022-37264 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in steal. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

steal vulnerable to Prototype Pollution via optionName variable

Also known asGHSA-8f8g-9j73-7p82
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 5, 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.35%2.03%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.

37other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
stealnpm
14Kdownloads / week

Description

Prototype pollution vulnerability in stealjs steal 2.2.4 via the optionName variable in main.js.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
📦npmstealall versionsNo fix

Affected Products

1 product · 1 configurations
Application
stealstealjs
1 version
2.2.4

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Remediation status

    The records we use list no patched version of steal for CVE-2022-37264. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    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 stealjs steal 2.2.4 via the optionName variable in main.js.
O3 Security · Impact-Aware SCA

Is CVE-2022-37264 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-37264: steal (Critical 9.8)