Skip to main content
CVE-2022-37265VulnerabilityPublished Updated

CVE-2022-37265: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.6% chance of exploitation in 30 days – higher than 76% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
npmstealjs/stealpkg:npm/stealjs/stealOther threatsAffected
  • =2.2.4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should first identify any usage of stealjs version 2.2.4 in their environments, including direct dependencies and transitive dependencies in web applications and development tools. Immediate steps include upgrading to a patched version of stealjs once available or applying community or vendor-provided patches if official fixes are delayed. In the interim, organizations should implement strict input validation and sanitization to prevent malicious payloads from reaching vulnerable code paths. Employing Content Security Policy (CSP) headers can help limit the impact of injected scripts. Additionally, monitoring application behavior for anomalies and deploying runtime application self-protection (RASP) tools can detect and block exploitation attempts. Regular dependency scanning and software composition analysis (SCA) should be enhanced to detect vulnerable versions proactively. Finally, organizations should engage with their software supply chain partners to ensure that patched versions are adopted promptly to prevent indirect exposure.

Description

Prototype pollution vulnerability in stealjs steal 2.2.4 via the alias variable in babel.js.

References

Community reviews

Loading reviews…