# CVE-2026-24832: Out-of-bounds write in ixray-1.6-stcop


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-wh8r-3r39-mcjj

## What is CVE-2026-24832?

CVE-2026-24832 is a critical vulnerability in ixray-team ixray-1.6-stcop, published on 27 Jan 2026. 

### Official description

Out-of-bounds Write vulnerability in ixray-team ixray-1.6-stcop.This issue affects ixray-1.6-stcop: before 1.3.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Ixray-Team Ix-Ray Engine 1.6.

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

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

## Is CVE-2026-24832 being exploited?

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

## Other vulnerabilities in ixray-team ixray-1.6-stcop

- [CVE-2026-24831](https://insights.sbomify.com/CVE-2026-24831/): Infinite loop (DoS) in ixray-1.6-stcop (high 7.5)
- [CVE-2026-24870](https://insights.sbomify.com/CVE-2026-24870/): Information disclosure in ixray-1.6-stcop (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24832 is a critical vulnerability in ixray-team ixray-1.6-stcop, published on 27 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2026-24832 in the wild and no public exploit code.

Affected product: ixray-team ixray-1.6-stcop. 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-24832/ (Markdown: https://insights.sbomify.com/CVE-2026-24832/index.md)
```

## Sources

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

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