# CVE-2026-92446: GUIX binary resource loader reads past the end of a resource, because no length for it ever reaches the loader


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/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-m779-jvp3-pmqr

## What is CVE-2026-92446?

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

### Official description

`gx_binres_theme_load()` and `gx_binres_font_load()` take the resource as a bare `GX_UBYTE *` with no length, and `GX_BINRES_DATA_INFO` has no field to carry one. Every read is therefore performed at an offset the file itself chose, against a buffer whose extent the loader does not know. A resource that declares more data than it contains is read past its end, and an offset stored in the file is turned into a pointer without being bounded.

This is a distinct defect from GHSA-hgcj-22cg-4hfv, which was an underflowed glyph count. It needs no underflow and no wrapped multiply: a perfectly well-formed, narrow glyph range reaches it.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-92446 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: Eclipse ThreadX - GUIX. 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-92446/ (Markdown: https://insights.sbomify.com/CVE-2026-92446/index.md)
```

## Sources

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

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