How severe is CVE-2026-92949?

CVE-2026-92949 has a CVSS 3.x base score of 4.0, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2026-92949 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (23rd percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-92949?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-92949 published?

CVE-2026-92949 was published on 2026-09-17 and last updated on 2026-09-21.

CVE-2026-92949

CVE-2026-92949 is a medium-severity vulnerability with a CVSS 3.x base score of 4.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-471.

Key facts

Severity: Medium (CVSS 3.x base score 4.0)
CVSS v4: 6.3
EPSS exploit prediction: 0% (23rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-471
Published: 2026-09-17
Last modified: 2026-09-21

Description

vm2 versions from 3.9.6 before 3.11.7 fail to properly restrict access to accessor properties on frozen objects, allowing sandboxed scripts to bypass vm.freeze() and vm.readonly() protections. Attackers can use Object.getOwnPropertyDescriptor() or __lookupSetter__() to extract and invoke host object setters directly, mutating properties the embedder explicitly marked read-only.

Frequently asked questions

What is CVE-2026-92949?: vm2 versions from 3.9.6 before 3.11.7 fail to properly restrict access to accessor properties on frozen objects, allowing sandboxed scripts to bypass vm.freeze() and vm.readonly() protections. Attackers can use Object.getOwnPropertyDescriptor() or __lookupSetter__() to extract and invoke host object setters directly, mutating properties the embedder explicitly marked read-only.
How severe is CVE-2026-92949?: CVE-2026-92949 has a CVSS 3.x base score of 4.0, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-92949 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (23rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-92949?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-92949 published?: CVE-2026-92949 was published on 2026-09-17 and last updated on 2026-09-21.

References

Other CWE-471 vulnerabilities

CVE-2026-50481 — Critical (CVSS 9.9): Modification of assumed-immutable data (maid) in Azure Active Directory allows an authorized attacker to elevate…
CVE-2022-25893 — Critical (CVSS 9.8): The package vm2 before 3.9.10 are vulnerable to Arbitrary Code Execution due to the usage of prototype lookup for the…
CVE-2018-3722 — High (CVSS 8.8): merge-deep node module before 3.0.1 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability, which…
CVE-2018-3720 — High (CVSS 8.8): assign-deep node module before 0.4.7 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability, which…
CVE-2018-3728 — High (CVSS 8.8): hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID)…
CVE-2024-55551 — High (CVSS 8.3): An issue was discovered in Exasol JDBC driver before 24.2.1 (2024-12-10). Attackers can inject malicious parameters…

Browse all CWE-471 vulnerabilities →