Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as limited shell user
-
ExploitInvoke shell operation bypassing privilege check
-
ExecutionExecute unauthorized privileged command
-
ImpactEscalate to full device control
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the VxWorks 7 command shell to be configured to enforce per-user command privileges (the vulnerable per-user privilege-enforcement mode), and the attacker must already hold an authenticated shell account with limited privileges. The flaw triggers only under 'certain shell operations' in which a command is evaluated without the normally-applied privilege check. Limiting factors: this is not exploitable against devices that do not use per-user command privilege enforcement, nor against devices where no low-privilege shell account exists or where the shell is not reachable by the attacker; a valid (if low-privilege) authenticated session is a hard prerequisite (PR:L), which meaningfully narrows the attacker population versus a fully unauthenticated flaw. |
| Impact | This is a genuine high-priority issue, not merely a high-CVSS-but-low-risk finding. The vendor CVSS of 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) indicates network-reachable, low-complexity exploitation requiring only limited (authenticated) privileges and no user interaction, yielding full confidentiality, integrity, and availability impact via privilege escalation. However, the AV:N rating warrants scrutiny: the flaw resides in the VxWorks command shell, so 'network' exploitability presumes the shell is remotely reachable (e.g., telnet/SSH/target shell exposed) and that the attacker already holds a valid low-privilege shell account - verify shell exposure with the vendor, as on devices where the shell is console/local-only the practical attack vector is local rather than network. No EPSS score, CISA KEV listing, or POC was provided; exploitation status is therefore 'no public exploit identified at time of analysis.' There is no SSVC data supplied. Net assessment: a serious authenticated privilege-escalation bug with a low exploitation bar for any user who already has limited shell access, but the realistic blast radius is bounded by whether/where the shell is exposed and whether per-user command privileges are enforced. |
| Exploit ScenarioDerived | An authenticated user holding a limited-privilege account on a VxWorks 7 command shell configured to enforce per-user command privileges issues a specifically sequenced shell operation that causes a command to be evaluated without the normal privilege check. The command executes with privileges the user was never granted, giving the attacker full control over the device. No public exploit code was identified at time of analysis; exploitation requires an existing low-privilege shell session. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Privilege escalation in Wind River VxWorks 7 (all versions up to 26.09) allows an authenticated low-privilege shell user to bypass the per-user command privilege check and execute commands they are not authorized to run, impacting confidentiality, integrity, and availability (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not universal: it requires the command shell to be configured in the vulnerable per-user command-privilege-enforcement mode and requires the attacker to already hold a valid low-privilege shell account, so devices that do not use that mode or expose no low-privilege shell are not affected. No public exploit identified at time of analysis, and the vendor has released a patch in version 26.09.
RemediationAI
Apply the vendor-released patch by upgrading Wind River VxWorks 7 to version 26.09, as confirmed in the vendor advisory at https://support2.windriver.com/index.php?page=cve&on=view&id=CVE-2026-104018; this is the primary and definitive fix. If immediate upgrade is not possible, reduce exposure by avoiding the vulnerable per-user command-privilege-enforcement mode where operationally feasible, removing or disabling unnecessary low-privilege shell accounts (a valid low-privilege account is a hard prerequisite, PR:L), restricting network reachability to the command shell (for example, management VLAN segmentation and firewall rules limiting SSH/Telnet access to trusted administrative hosts), and logging or alerting on shell command usage that exceeds expected low-privilege activity; each compensating control carries trade-offs such as reduced operational flexibility or increased access-management overhead and should be treated as temporary until 26.09 can be deployed.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-269 improper privilege management in the Wind River VxWorks 7 command shell when configured to enforce per-user command privileges. Under certain shell operations, a command is evaluated before or without the privilege check that is normally applied, so an authenticated user with limited privileges can invoke commands reserved for higher-privileged users. VxWorks 7 is a real-time operating system widely embedded in industrial, medical, networking, and other devices, so a shell privilege-escalation flaw can translate into full compromise of the affected device's confidentiality, integrity, and availability. The affected product is tracked by CPE cpe:2.3:a:wind_river_systems_inc:vxworks_7:*:*:*:*:*:*:*:* covering all versions up to 26.09; the vendor advisory is at https://support2.windriver.com/index.php?page=cve&on=view&id=CVE-2026-104018.
Know when Vxworks 7 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Authenticated limited shell user (PR:L) reaches the flaw over a network-exposed shell (AV:N) with a reliable operation (AC:L), escalating to full device control (C/I/A:H).
Primary rating from Vendor (WindRiver).
CVSS VectorVendor: WindRiver
DescriptionCVE.org
An improper privilege management vulnerability (CWE-269) exists in the command shell of Wind River VxWorks 7 all versions up to 26.09. when configured to enforce per-user command privileges. Under certain shell operations, a command may be evaluated without the privilege check that is normally applied, allowing an authenticated user with limited privileges to execute commands they are not authorized to run. Successful exploitation can result in privilege escalation, with impact to the confidentiality, integrity, and availability of the affected device. Fixed in 26.09
Executive ViewAI
Wind River VxWorks 7, the real-time operating system embedded in long-lived industrial, medical, aerospace, and networking equipment, contains a high-severity privilege-escalation flaw that allows an attacker who already holds a valid low-privilege shell account to bypass per-user command restrictions and execute commands they are not authorized to run, compromising the confidentiality, integrity, and availability of the affected device. Leadership should care because these devices are typically difficult to service and often network-exposed, so a single compromised low-privilege account can translate into unauthorized control of equipment that supports safety, production, or customer-facing services. Exposure is limited to devices configured in the vulnerable per-user command-privilege-enforcement mode that also expose a low-privilege shell; units without that mode or without such shell access are not affected, making the at-risk footprint definable and prioritizable.
Apply vendor patch: VxWorks 7 version 26.09.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Memory corruption in Wind River VxWorks 7 occurs when a task passes crafted arguments to a specific system call, causing
Local denial of service in Wind River VxWorks 7 (all releases prior to 26.09) lets a low-privileged local task exhaust k
Memory pool exhaustion in Wind River VxWorks 7 releases 24.03 through 26.03 can terminate system operations when specifi
Local resource exhaustion in Wind River VxWorks 7 (versions prior to 26.09) allows a low-privileged local application to
EUVD-2026-90976
GHSA-fjrv-5j96-cvhx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB