CISA ADP Vulnrichment

Answer in brief

CVE-2026-102711 records a Medium severity (CVSS 5.6) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps Eclipse Foundation/`eclipse-threadx/threadx` (module manager / loadable-module loader) (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 29, 2026Updated Sep 29, 2026Source checked Sep 30, 2026First seen by HOL Sep 29, 2026Material review Sep 29, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.6
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.6. 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 Eclipse Foundation/`eclipse-threadx/threadx` (module manager / loadable-module loader) (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Eclipse Foundation/`eclipse-threadx/threadx` (module manager / loadable-module loader)generic	current HEAD and prior (the `_txm_module_manager_*_load` APIs take no image length).	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Eclipse Foundation/`eclipse-threadx/threadx` (module manager / loadable-module loader).
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 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 29, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

Two issues in the ThreadX loadable-module loader, reached when a device loads an attacker-controlled module object via `_txm_module_manager_memory_load` / `_txm_module_manager_in_place_load` — APIs that take ONLY a base pointer, no image length, so every size/offset field in `TXM_MODULE_PREAMBLE` is fully attacker-trusted: (1) a heap OOB **read** (`code_size` trusted as the source-image length in the code-copy loop), and (2) a control-flow-integrity / defense-in-depth gap (module entry/start/callback/stop pointers computed as `code_start + preamble_offset` with only a `!= 0` check, and the preamble `checksum` never verified). No controlled OOB write was found (honest — the copy destination is overflow-guarded).

Quoted source text, attributed separately from HOL analysis.