# CVE-2026-92449: `_gx_binres_pixelmap_table_load()` in the GUIX binary resource (theme) loader indexes the pixelmap table with a value read verbatim from the


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/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-m85v-2ccm-w6gf

## What is CVE-2026-92449?

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

### Official description

`_gx_binres_pixelmap_table_load()` in the GUIX binary resource (theme) loader indexes the pixelmap table with a value read verbatim from the resource file and never bounds it against the table size. A crafted theme drives a write of up to roughly 256 KB past the end of the table.

The overflowed buffer is allocated by GUIX itself, through `_gx_system_memory_allocator`, rather than supplied by the caller, so the loader corrupts its own arena. The public API `gx_binres_theme_load()` takes no size parameter, so no amount of caller diligence prevents this.

Reproduces in the shipped default configuration; `GX_BINARY_RESOURCE_SUPPORT` is enabled by default.

Weakness: CWE-787 (Out-of-bounds Write), CWE-457 (Use of Uninitialized Variable), CWE-129 (Improper Validation of Array Index)

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


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

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

## Is CVE-2026-92449 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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