CVE-2026-65057
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKeep (commit 91c75e0) contains a server-side request forgery vulnerability that allows unauthenticated attackers to make the backend issue arbitrary HTTP requests by supplying attacker-controlled host values to the unprotected healthcheck endpoint. Attackers can send a crafted JSON payload with a malicious host parameter to cause the backend to issue outbound requests to internal services or cloud metadata endpoints, enabling theft of cloud credentials and internal network reconnaissance.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceKeep contains a server-side request forgery (SSRF) vulnerability in its unprotected healthcheck endpoint. Unauthenticated attackers can send a crafted JSON payload with a malicious host parameter, causing the backend to issue arbitrary HTTP requests to internal services or cloud metadata endpoints, enabling credential theft and internal network reconnaissance.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Keep software is installedLocate Keep installation directories or check running processes for the Keep applicationAffected if Keep is installed and the version is within the affected range (if known)
-
Locate the healthcheck endpointReview application routing/configuration files to identify healthcheck or heartbeat endpoints; common paths include /health, /healthcheck, /ping, or similarAffected if A healthcheck endpoint exists and is reachable without authentication
-
Verify healthcheck endpoint authenticationSend a request to the healthcheck endpoint without credentials and observe if the response is successfulAffected if The healthcheck endpoint returns valid responses without requiring authentication
-
Test host parameter controllabilitySend a crafted JSON payload to the healthcheck endpoint with an attacker-controlled host parameter (e.g., internal IP or cloud metadata URL) and observe if the server performs the requestAffected if The server accepts and executes HTTP requests to arbitrary hosts specified in the host parameter
-
Check for internal network restrictionsAttempt to trigger requests to known internal addresses (127.0.0.1, 169.254.169.254 for AWS IMDS, or other internal ranges) and verify if these are blockedAffected if The healthcheck endpoint allows requests to internal IPs, localhost, or cloud metadata services without restriction
You are affected if Keep is installed with an unauthenticated healthcheck endpoint that allows user-controlled host parameters and does not block requests to internal addresses or cloud metadata services.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict access to the healthcheck endpoint (require authentication or network-level access control) and implement host validation to block requests to internal/private IP ranges and cloud metadata endpoints (e.g., 169.254.169.254).
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-65057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-65057 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data