CVE-2026-97686: Wind River VxWorks 7 IPNET subsystem memory leak

CVE-2026-97686 · 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 IPNET networking subsystem fails to properly release kernel memory and file descriptors when certain system calls are made, causing resource exhaustion and potential denial of service when applications terminate.

Technologies: Wind River VxWorks 7. Vendors: Wind River.

Quick answers

Is CVE-2026-97686 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-97686 being exploited in the wild.
How severe is CVE-2026-97686?
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-97686?
A patch was published on 2026-09-28: Fixed in VxWorks 7 version 26.09 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-97686 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-97686?
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 resource leak in the IPNET subsystem fails to release allocated kernel memory and file descriptors when specific system call arguments cause the calling application to terminate. The vulnerability is triggered via crafted system call arguments without requiring authentication or user interaction. An attacker can exhaust system resources (memory and file descriptors) leading to denial of service. The vulnerability was fixed in VxWorks 7 version 26.09.

Affected products

  • Wind River VxWorks 7 prior to 26.09

Timeline

  • 2026-09-28: disclosed
  • 2026-09-28: patched: Fixed in VxWorks 7 version 26.09

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.