VxWorks 7 Memory allocation

Why this deserves its current priority

CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Wind River Systems Inc/VxWorks 7 (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Wind River Systems Inc/VxWorks 7.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 28, 2026

Sources and claim methodology

• Source referencesupport2.windriver.com

Related CVEs

• VxWorks Memory AllocationAlso CWE-401
• Unsafe use of eval() method in ros2 topic hz toolSame generic ecosystem
• ZoneMinder 1.37.x Path Traversal via files viewSame generic ecosystem
• DOMSanitizer - Incomplete data: URL Sanitization in DOMSanitizer::isDangerousUrl() Allows Base64-Encoded Payloads to Bypass href and xlink:href ValidationSame generic ecosystem
• InvoicePlane: Incomplete Authorization Remediation in Users::form() Enables Primary Administrator Account Takeover via Email Reassignment and Password RecoverySame generic ecosystem
• InvoicePlane: Primary Administrator Privilege Downgrade via `Users::form()` (Missing Object-Level Authorization)Same generic ecosystem