# CVE-2026-59683: OpenRGB: local and remote system compromise via arbitrary file write using attacker controlled strings

> Attackers can write arbitrary files via the network protocol, leading to system compromise or account takeover in OpenRGB.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/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-59683, GHSA-3c7q-x53x-mrfx, UBUNTU-CVE-2026-59683

## What is CVE-2026-59683?

CVE-2026-59683 is a critical path traversal 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 to write attacker controlled strings into arbitrary file system paths (extension of CVE-2026-59682). This allows either a full system compromise from local or remote (if the daemon is running as root) or a full account takeover (if the daemon is running in user context).

Weakness: CWE-73 (External Control of File Name or Path)

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


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

Apply the vendor's patch.

## Is CVE-2026-59683 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59683 is a critical path traversal 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-59683 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-59683/ (Markdown: https://insights.sbomify.com/CVE-2026-59683/index.md)
```

## Sources

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

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