VxWorks Memory Allocation

Answer in brief

CVE-2026-102005 records a Medium severity (CVSS 5.5) vulnerability in VxWorks Memory Allocation. The current sources do not mark it as known exploited. The current feed maps Wind River Inc/VxWorks 7 (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 28, 2026Updated Sep 28, 2026Source checked Sep 28, 2026First seen by HOL Sep 28, 2026Material review Sep 28, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

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.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

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

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Wind River Inc/VxWorks 7generic	VxWorks 7	Not reported

Recommended response

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

Evidence timeline and material changes

Published upstream
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 28, 2026

Sources and claim methodology

Source referencesupport2.windriver.com

Upstream source description

Wind River VxWorks 7 24.03 through 26.03, a memory leak occurs under specific, non-default configuration states when processing specific service routines, causing the system to terminate operations before releasing allocated memory pools. Fixed in VxWorks 7 26.09

Quoted source text, attributed separately from HOL analysis.