Security readout for executives and security teams
Plain-English summary
Keep at commit 91c75e0 exposes an unauthenticated health-check function that can make backend HTTP requests to attacker-selected hosts. An attacker could use the server’s trusted network position to reach internal systems or cloud metadata, potentially exposing cloud credentials. Publicly reachable deployments warrant urgent review.
Executive priority
Prioritize immediate exposure assessment and containment for Internet-accessible Keep deployments. Credential theft could expand impact beyond Keep into cloud resources. Because the sources do not identify a specific fixed release, assign ownership to track vendor guidance, verify remediation, and investigate possible prior abuse.
Technical view
CVE-2026-65057 is a CWE-918 server-side request forgery in POST /providers/healthcheck. Attacker-controlled host input reaches backend outbound-request logic without authentication. CVSS 3.1 scores it 9.3 because exploitation is remote, low-complexity, and requires neither privileges nor user interaction, with potentially high confidentiality impact.
Likely exposure
Exposure is highest where Keep at the identified commit is deployed and /providers/healthcheck is reachable by untrusted users. Impact depends on the backend’s outbound network access, including connectivity to internal services or cloud metadata. The supplied affected-version value, “0,” does not establish a clear release range.
Exploitation context
The sources describe a crafted-request attack path, but the supplied record is not in CISA KEV and provides no evidence of active exploitation. Treat the endpoint as readily testable by unauthenticated attackers without assuming exploitation has occurred.
Researcher notes
The record identifies commit 91c75e0 and an unauthenticated host-controlled SSRF path. Release-level affected and fixed boundaries remain unclear, and no definitive patch version is supplied. Validation should focus on route accessibility, input-to-request flow, egress reachability, and logs, without sending requests toward sensitive internal or metadata services.
Mitigation direction
- Check Keep’s current vendor guidance and upgrade when a documented fixed release is identified.
- Restrict untrusted access to /providers/healthcheck until remediation is confirmed.
- Limit backend outbound connectivity to approved destinations and block cloud metadata access where unnecessary.
- Rotate potentially exposed cloud credentials if logs or telemetry indicate suspicious outbound requests.
Validation and detection
- Identify deployed Keep versions and compare their commit ancestry with 91c75e0.
- Confirm whether unauthenticated users can reach POST /providers/healthcheck.
- Review proxy and application logs for unusual health-check requests or attacker-selected destinations.
- Inspect outbound telemetry for Keep connections to internal services, metadata addresses, or unexpected hosts.
- Verify network controls prevent Keep from reaching sensitive destinations without business need.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-65057 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N3.94.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub IssueCVE reference, VulnCheck · issue-tracking
- ProductCVE reference, VulnCheck · patch
- https://www.vulncheck.com/advisories/keep-unauthenticated-server-side-request-forgery-via-post-providers-healthcheckCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.