# CVE-2026-18794: OpenRGB: insufficient input data checks lead to Denial-of-Service, memory overread and overwrite

> Attackers can cause denial of service and potential code execution in OpenRGB via inconsistent network protocol data.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-18794, GHSA-2hph-9m2g-p27v, UBUNTU-CVE-2026-18794

## What is CVE-2026-18794?

CVE-2026-18794 is a high-severity memory corruption vulnerability in CalcProgrammer1 OpenRGB, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OpenRGB network protocol allows attackers to cause memory exhaustion and out-of-bounds memory reads and writes by passing inconsistent data.

Weakness: CWE-1288 (Improper Validation of Consistency within Input)

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


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

Apply the vendor's patch.

## Is CVE-2026-18794 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18794 is a high-severity memory corruption vulnerability in CalcProgrammer1 OpenRGB, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18794 in the wild and no public exploit code.

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

## Sources

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

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