# CVE-2026-94023: Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/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-36vf-7cx6-9f9j

## What is CVE-2026-94023?

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

### Official description

A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex.

Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.

Weakness: CWE-862 (Missing Authorization), CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-94023 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94023 is a medium-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94023 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-94023/ (Markdown: https://insights.sbomify.com/CVE-2026-94023/index.md)
```

## Sources

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

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