# CVE-2026-59682: Arbitrary file overwrite and deletion local and remote in OpenRGB

> Attackers can overwrite or delete arbitrary files via the SAVE_PROFILE message in OpenRGB, potentially compromising system integrity.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/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-59682, GHSA-26mm-mg9c-fjp5, UBUNTU-CVE-2026-59682, openSUSE-SU-2026:11602-1

## What is CVE-2026-59682?

CVE-2026-59682 is a high-severity 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

Arbitrary file overwrite via SAVE_PROFILE message in OpenRGB. This issue affects OpenRGB through 1.0rc3.

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `OpenRGB` | openSUSE:Tumbleweed | All versions | 1.0~rc3.1+git0.g5e81e26f-1.1 |

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

Apply the vendor's patch.

## Is CVE-2026-59682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59682 is a high-severity 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-59682 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-59682/ (Markdown: https://insights.sbomify.com/CVE-2026-59682/index.md)
```

## Sources

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

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