# CVE-2026-108980: Path traversal in Blinko

> Authenticated attackers can exploit path traversal in plugin installation to overwrite root-owned files and achieve remote code execution as root.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-q62g-66hr-78pq

## What is CVE-2026-108980?

CVE-2026-108980 is a high-severity path traversal vulnerability in Blinko, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Blinko through 1.8.8 allows directory traversal, overwriting startup files as root, via installPlugin. It builds the plugin install path from an unsanitized name in server/routerTrpc/plugin.ts, and the plugin.installPlugin tRPC procedure is open to any authenticated user. Thus, a name containing ../ sequences writes the downloaded plugin files outside the plugins directory. Because the official Docker image runs as root, an authenticated attacker overwrites a root-owned startup file and achieves remote code execution as root. Self-registration for an account may be possible.

Weakness: CWE-24 (Path Traversal: '../filedir')

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


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

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

## Is CVE-2026-108980 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108980 is a high-severity path traversal vulnerability in Blinko, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108980 exists.

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

## Sources

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

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