# CVE-2026-95109: Cortex-A7 module data validation checks only the first address of a caller-supplied range


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-fvp6-37q5-c648

## What is CVE-2026-95109?

CVE-2026-95109 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 

### Official description

The Cortex-A7 MMU Modules port validates a caller-supplied buffer by translating **one address** — the first byte. The common Module Manager hands its range check the module instance, the start address and the complete byte size; the Cortex-A7 implementation discarded the instance and the size and asked the MMU a single question about the start.

A memory-protected module therefore passed any range whose first byte was user-readable, however far the rest of it reached. Privileged dispatch code then read or wrote the whole range. Because every protected-module dispatcher that consumes a buffer or an extra-parameter array goes through this one macro, the defect is not in any individual service: it is in the primitive all of them rely on.

Weakness: CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-95109?


## How do I fix CVE-2026-95109?

No fix has been published for CVE-2026-95109 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95109 being exploited?

There is no known exploitation of CVE-2026-95109 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95109 and fix it if it is affected.

What it is: CVE-2026-95109 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-95109 in the wild and no public exploit code.

Affected product: Eclipse ThreadX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95109/ (Markdown: https://insights.sbomify.com/CVE-2026-95109/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95109
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95109
- OSV: https://osv.dev/vulnerability/CVE-2026-95109

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95109/
Summaries are generated and may contain mistakes; the official description above is the record.