Vxworks 7
Monthly
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.
Memory corruption in Wind River VxWorks 7 occurs when a task passes crafted arguments to a specific system call, causing an out-of-bounds write inside the RTOS memory-management subsystem and giving the caller full confidentiality, integrity, and availability impact on the running instance (CVSS 3.1 7.8 HIGH). The flaw is local in nature - per the vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) the attacker must already execute code on the device as at least a low-privileged task, so only VxWorks 7 deployments that run untrusted or lower-trust code are realistically exposed; locked-down devices that execute only vendor-signed firmware are not remotely reachable through this bug. All VxWorks 7 builds prior to version 26.09 are affected, and there is no public exploit code or CISA KEV entry identified at time of analysis.
Local denial of service in Wind River VxWorks 7 (all releases prior to 26.09) lets a low-privileged local task exhaust kernel memory by invoking process-management system calls whose specific arguments cause the subsystem to skip freeing allocated kernel memory when the calling application terminates. Repeated invocation accumulates the leak until the kernel memory pool is depleted, producing a high availability impact (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited; Wind River has fixed it in VxWorks 7 version 26.09.
Memory pool exhaustion in Wind River VxWorks 7 releases 24.03 through 26.03 can terminate system operations when specific service routines are invoked while the device is in a non-default configuration state, because allocated memory pools are not released before the failure propagates. The weakness is local and availability-focused (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H per independent assessment): an attacker needs low-privileged local execution on the RTOS and the affected services must be reachable, and no user interaction or network path is required. Default installations are not affected, the configuration prerequisite plus the local-access requirement substantially narrow the realistic attacker population, and no public exploit identified at time of analysis; Wind River has fixed the issue in VxWorks 7 26.09. Overall this is a moderate-severity, low-real-world-priority issue rather than a broadly exploitable one.
Local resource exhaustion in Wind River VxWorks 7 (versions prior to 26.09) allows a low-privileged local application to leak kernel memory and system file descriptors by invoking system calls with specific argument values, causing the IPNET subsystem to fail to release those resources before the calling application terminates. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 5.5), an attacker must already be executing code on the device, so this is an availability-only denial-of-service rather than a remote or unauthenticated attack, and there is no confidentiality or integrity impact. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); Wind River has released a fixed version, 26.09, so the primary remediation is a firmware upgrade.
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.
Memory corruption in Wind River VxWorks 7 occurs when a task passes crafted arguments to a specific system call, causing an out-of-bounds write inside the RTOS memory-management subsystem and giving the caller full confidentiality, integrity, and availability impact on the running instance (CVSS 3.1 7.8 HIGH). The flaw is local in nature - per the vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) the attacker must already execute code on the device as at least a low-privileged task, so only VxWorks 7 deployments that run untrusted or lower-trust code are realistically exposed; locked-down devices that execute only vendor-signed firmware are not remotely reachable through this bug. All VxWorks 7 builds prior to version 26.09 are affected, and there is no public exploit code or CISA KEV entry identified at time of analysis.
Local denial of service in Wind River VxWorks 7 (all releases prior to 26.09) lets a low-privileged local task exhaust kernel memory by invoking process-management system calls whose specific arguments cause the subsystem to skip freeing allocated kernel memory when the calling application terminates. Repeated invocation accumulates the leak until the kernel memory pool is depleted, producing a high availability impact (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited; Wind River has fixed it in VxWorks 7 version 26.09.
Memory pool exhaustion in Wind River VxWorks 7 releases 24.03 through 26.03 can terminate system operations when specific service routines are invoked while the device is in a non-default configuration state, because allocated memory pools are not released before the failure propagates. The weakness is local and availability-focused (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H per independent assessment): an attacker needs low-privileged local execution on the RTOS and the affected services must be reachable, and no user interaction or network path is required. Default installations are not affected, the configuration prerequisite plus the local-access requirement substantially narrow the realistic attacker population, and no public exploit identified at time of analysis; Wind River has fixed the issue in VxWorks 7 26.09. Overall this is a moderate-severity, low-real-world-priority issue rather than a broadly exploitable one.
Local resource exhaustion in Wind River VxWorks 7 (versions prior to 26.09) allows a low-privileged local application to leak kernel memory and system file descriptors by invoking system calls with specific argument values, causing the IPNET subsystem to fail to release those resources before the calling application terminates. Per the assessed vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 5.5), an attacker must already be executing code on the device, so this is an availability-only denial-of-service rather than a remote or unauthenticated attack, and there is no confidentiality or integrity impact. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); Wind River has released a fixed version, 26.09, so the primary remediation is a firmware upgrade.