# CVE-2026-102804: Nothings stb stb_hexwave.h hexwave_init integer overflow

> An integer overflow in stb_hexwave.h allows remote attackers to cause denial of service or potentially execute code via crafted width/oversample arguments.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-102804, GHSA-x842-766r-cjq8, UBUNTU-CVE-2026-102804

## What is CVE-2026-102804?

CVE-2026-102804 is a medium-severity vulnerability in Nothings stb, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in Nothings stb up to 2c980bb59875b0d32144a71867fbdebb2f77cd20. The impacted element is the function hexwave_init in the library stb_hexwave.h. Performing a manipulation of the argument width/oversample results in integer overflow. Remote exploitation of the attack is possible. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-189

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


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

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

## Is CVE-2026-102804 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102804 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102804 is a medium-severity vulnerability in Nothings stb, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102804 exists.

Affected product: Nothings stb. 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-102804/ (Markdown: https://insights.sbomify.com/CVE-2026-102804/index.md)
```

## Sources

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

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