vm2: Use of Incorrectly-Resolved Name or Reference
CVE-2026-92951 is a critical-severity use of incorrectly-resolved name or reference vulnerability in vm2 from Patriksimek, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 3.11.7 as the first without the flaw, so updating vm2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update vm2 to 3.11.7 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Patriksimek | vm2 | before 3.11.7 | 3.11.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (vulncheck.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.4 | Critical | CNA (vulncheck.com) |
| CVSS 3.1 | 9.9 | Critical | CNA (vulncheck.com) |
Official description
vm2 before 3.11.7 contains an incorrect authorization vulnerability in the external package allowlist check that uses non-exact substring matching instead of full package-name boundary validation. Attackers can bypass the allowlist by requiring a colliding package name that contains an allowlisted package substring, causing vm2 to load and execute unauthorized host packages in the host context.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Incorrectly-Resolved Name or Reference
The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
More Use of Incorrectly-Resolved Name or Reference vulnerabilities (CWE-706)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Other references
Other vulnerabilities in vm2
- 7.5 High severity
- 9.0 Critical severity
- 10.0 Critical severity
- 10.0 Critical severity
- 7.2 High severity
- 10.0 Critical severity
Recent Use of Incorrectly-Resolved Name or Reference vulnerabilities
- 8.1 High severity
- 8.1 High severity
- 8.3 High severity
- 9.0 Critical severity
- 9.6 Critical severity
- 9.6 Critical severity
Spotted an error? Tell us.