How severe is CVE-2026-92947?

No CVSS score has been assigned to CVE-2026-92947 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-92947?

CVE-2026-92947 affects the following packages: vm2 (npm). Ecosystems affected: npm.

How do I fix CVE-2026-92947?

Update vm2 to 3.11.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-92947 is resolved across your whole dependency graph.

How do I detect CVE-2026-92947 in my npm dependencies?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2026-92947 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-92947 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-2026-92947?

CVE-2026-92947 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-2026-92947?

CVE-2026-92947 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-92947 published, and has it been updated?

CVE-2026-92947 was published on September 17, 2026 and was last updated on October 28, 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

CVE-2026-92947 — vm2

Fix: patriksimek/vm2@4f2508a

CVE-2026-92947 is a Information Exposure vulnerability in vm2. A fix is available for vm2 — see the affected versions and patch details below.

vm2 before 3.11.7 Memory Disclosure via Buffer Pool

Also known asGHSA-fcqc-726x-5wfc

Published

Sep 17, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-92947.

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.

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.

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

vm2npm

1.3Mdownloads / week

Description

Summary

Sandboxed code is able to disclose host memory used by small allocations by Buffer.from, Buffer.concat.

Details

vm2 exposes Buffer object to sandboxed code by default. Small Buffer allocations (for example, Buffer.allocUnsafe(), Buffer.from(array), Buffer.from(string), and Buffer.concat()) use the same Buffer pool, which is shared with the sandbox. This allows sandboxed code to disclose host memory used by the functions listed above.

PoC

Tested against [email protected] in the node REPL.

Buffer.from('host-memory-should-not-leak-to-sandbox')
new (require('vm2').VM)().run(`Buffer.from(Buffer.from([0]).buffer, 0, Buffer.from([0]).buffer.byteLength).toString('ascii')`)

Impact

Since sandbox acquires an ArrayBuffer that is used by the host, it can disclose sensitive data going through functions mentioned above and even write to these buffers, which can lead to sensitive data exposure and potentially denial-of-service.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vm2`	all versions	3.11.7`npm install vm2@3.11.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vm2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vm2 to 3.11.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-92947 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is rated as an Important severity flaw because an attacker capable of executing arbitrary code within a sandboxed runtime can breach isolation boundaries, accessing and modifying data stored in host-realm memory. In affected Red Hat products, services running untrusted JavaScript inside sandboxed…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2026-92947 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.1	`ansible-automation-platform/automation-portal:1791295379`	RHSA-2026:80603
Red Hat Ansible Automation Platform 2.2	`ansible-automation-platform/automation-portal:1791293780`	RHSA-2026:80644
Red Hat Ansible Automation Platform 2.2	`ansible-automation-platform/bootc-automation-portal-rhel9:1791865660`	RHSA-2026:82151
Red Hat Developer Hub 1.10	`rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend:1791242697`	RHSA-2026:76788
Red Hat Developer Hub 1.10	`rhdh/rhdh-hub-rhel9:1791311495`	RHSA-2026:79088
Red Hat Developer Hub 1.9	`rhdh/rhdh-hub-rhel9:1793117813`	RHSA-2026:91651

Frequently Asked Questions

### Summary Sandboxed code is able to disclose host memory used by small allocations by `Buffer.from`, `Buffer.concat`. ### Details vm2 exposes `Buffer` object to sandboxed code by default. Small [`Buffer` allocations](https://nodejs.org/api/buffer.html#static-method-bufferallocunsafesize) (for example, [Buffer.allocUnsafe()](https://nodejs.org/api/buffer.html#static-method-bufferallocunsafesize), [Buffer.from(array)](https://nodejs.org/api/buffer.html#static-method-bufferfromarray), [Buffer.from(string)](https://nodejs.org/api/buffer.html#static-method-bufferfromstring-encoding), and [Buffer

O3 Security · Impact-Aware SCA

Is CVE-2026-92947 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works