CVE-2026-67594
Unauthenticated API access enables full server control due to missing CipiAuth middleware.
Is CVE-2026-67594 being exploited?
Not confirmed. CVE-2026-67594 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-67594?
CVE-2026-67594 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67594?
Not known from our data. No patch reference has been recorded for CVE-2026-67594, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-67594 affect?
CVE-2026-67594 affects Spikster (Cipi) API / Control Panel, Hosts managed by Cipi, Databases provisioned via Cipi. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67594?
Isolate/block API, apply vendor patch when released, rotate root/DB creds, audit logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can access ~50 API endpoints to enumerate/provision servers, reset root passwords, read/write host files, and create DB users.
Immediate action required
- affected<= e1cdf8c4b780c87457b548c38a87982b549e2465
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.