# CVE-2026-67594: Spikster Missing Authentication via API Route Group

> Unauthenticated attackers can access all API routes to provision servers, reset passwords, and read/write files due to missing middleware application.

- **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:** No
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-rg37-h5w6-fj69

## What is CVE-2026-67594?

CVE-2026-67594 is a critical missing authorization vulnerability in yolanmees Spikster, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Spikster through commit e1cdf8c contains a missing authentication vulnerability that allows unauthenticated remote attackers to access all API routes by exploiting the unattached CipiAuth middleware, which is registered but never applied to any route in the API routing configuration. Attackers can invoke approximately 50 unprotected API endpoints to enumerate and provision servers, reset root passwords, read and write arbitrary files on the host, and create database users.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-67594 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67594 is a critical missing authorization vulnerability in yolanmees Spikster, published on 30 Jul 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-67594 in the wild and no public exploit code.

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

## Sources

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

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