CVE-2026-65057
Unauth SSRF in Keep healthcheck allows backend requests to internal/cloud endpoints.
Is CVE-2026-65057 being exploited?
Not confirmed. CVE-2026-65057 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.43% probability of exploitation in the next 30 days.
How severe is CVE-2026-65057?
CVE-2026-65057 is rated Critical with a CVSS score of 9.2. 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-65057?
Not known from our data. No patch reference has been recorded for CVE-2026-65057, 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-65057 affect?
CVE-2026-65057 affects Keep (commit 91c75e0), Self-hosted Keep instances, Servers exposing the vulnerable healthcheck endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-65057?
Restrict/validate healthcheck host input, block metadata endpoints, restrict access and apply patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated SSRF lets attackers make backend HTTP requests to internal services and cloud metadata, enabling credential theft and internal reconnaissance.
Immediate action required
- affected<= 91c75e0
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.