# CVE-2026-102006: Wind River VxWorks 7 kernel memory leak in process management

Source: https://junglewise.ai/threats/cve-2026-102006-in-wind-river-vxworks-7-prior-to-26-09-specific-system-call  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-28. Updated: 2026-09-28  
License: CC BY 4.0 with a link back

CVE-2026-102006 · Severity: medium · CVSS 5.5 · Published 2026-09-28

Wind River VxWorks 7 is a real-time operating system used in embedded systems and critical infrastructure. A memory leak vulnerability in the process management subsystem allows a local attacker to exhaust kernel memory and cause a denial of service by terminating applications with specific system call arguments, potentially crashing the device or causing system instability.

Technologies: [Wind River VxWorks 7](https://junglewise.ai/threats/technologies/vxworks-7). Vendors: [Wind River](https://junglewise.ai/threats/vendors/wind-river).

## Quick answers

**Is CVE-2026-102006 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-102006 being exploited in the wild.

**How severe is CVE-2026-102006?** Medium severity, with a CVSS score of 5.5, published 28 September 2026.

**Which products and versions are affected?** Wind River VxWorks 7 prior to 26.09.

**Is there a fix for CVE-2026-102006?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-102006 attacked?** It is attacked with local access, in an operating system.

**Am I affected by CVE-2026-102006?** Check whether you run Wind River VxWorks 7 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A memory leak exists in the VxWorks 7 process management subsystem where certain system call arguments prevent proper deallocation of kernel memory when a process terminates. The vulnerability requires local access to invoke affected system calls. An attacker can repeatedly trigger this condition to exhaust kernel memory, leading to denial of service.

## Affected products

- Wind River VxWorks 7 prior to 26.09

## Timeline

- 2026-09-28: disclosed

## References

- [https://support2.windriver.com/index.php?page=cve](https://support2.windriver.com/index.php?page=cve)

## Related threats

- [Wind River VxWorks 7 privilege escalation in command shell](https://junglewise.ai/threats/cve-2026-104018-an-improper-privilege-management-vulnerability-cwe-269-exists-in)
- [Wind River VxWorks 7 memory leak in service routine processing](https://junglewise.ai/threats/cve-2026-102005-wind-river-vxworks-7-24-03-through-26-03-a-memory-leak-occurs)
- [Wind River VxWorks 7 memory corruption in system call handling](https://junglewise.ai/threats/cve-2026-102004-wind-river-vxworks-7-prior-to-26-09-specific-system-call)
- [Wind River VxWorks 7 IPNET subsystem memory leak](https://junglewise.ai/threats/cve-2026-97686-wind-river-vxworks-7-prior-to-26-09-specific-system-call)