# CVE-2026-28427: OpenDeck affected by path traversal allows arbitrary file read

> An attacker can read arbitrary files by exploiting a path traversal vulnerability in the OpenDeck local web service.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-4974-g27q-h5m8

## What is CVE-2026-28427?

CVE-2026-28427 is a medium-severity path traversal vulnerability in nekename OpenDeck, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OpenDeck is Linux software for your Elgato Stream Deck. Prior to 2.8.1, the service listening on port 57118 serves static files for installed plugins but does not properly sanitize path components. By including ../ sequences in the request path, an attacker can traverse outside the intended directory and read any file OpenDeck can access. This vulnerability is fixed in 2.8.1.

Weakness: CWE-24 (Path Traversal: '../filedir'), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Nekename Opendeck.

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

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

## Is CVE-2026-28427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28427 is a medium-severity path traversal vulnerability in nekename OpenDeck, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-28427 in the wild and no public exploit code.

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

## Sources

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

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