CVE-2026-65057

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-21. a secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Keep (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.

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
73(Attend)
EG Risk 73/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

Keep Unauthenticated Server-Side Request Forgery via POST /providers/healthcheck | Advisories | VulnCheck

https://www.vulncheck.com/advisories/keep-unauthenticated-server-side-request-forgery-via-post-providers-healthcheck
generic

Unauthenticated Server-Side Request Forgery via POST /providers/healthcheck · Issue #6630 · keephq/keep · GitHub

https://github.com/keephq/keep/issues/6630
generic

GitHub - keephq/keep: The open-source AIOps and alert management platform · GitHub

https://github.com/keephq/keep

Vendor Advisories for CVE-2026-65057(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 02:44 UTCGHSA enrichment
  2. 2026-07-26 22:35 UTCGHSA enrichment
  3. 2026-07-26 18:24 UTCEG score recompute
  4. 2026-07-26 18:24 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:09 UTCEG score recompute
  8. 2026-07-26 14:09 UTCGHSA enrichment
  9. 2026-07-26 09:59 UTCGHSA enrichment
  10. 2026-07-26 04:18 UTCEG score recompute
  11. 2026-07-26 04:18 UTCGHSA enrichment
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 14:18 UTCEPSS rescore
  14. 2026-07-24 14:18 UTCEPSS rescore
  15. 2026-07-24 14:18 UTCEPSS rescore
  16. 2026-07-23 14:18 UTCEPSS rescore
  17. 2026-07-23 14:18 UTCEPSS rescore
  18. 2026-07-23 03:22 UTCEG score recompute
  19. 2026-07-22 22:57 UTCEG score recompute
  20. 2026-07-22 22:57 UTCGHSA enrichment
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 21:22 UTCEG score recompute
  24. 2026-07-21 21:09 UTCEG score recompute
  25. 2026-07-21 21:08 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-65057?
CVE-2026-65057 is a critical vulnerability published on July 21, 2026. Keep (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…
When was CVE-2026-65057 disclosed?
CVE-2026-65057 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65057 actively exploited?
CVE-2026-65057 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.1% of all scored CVEs.
What is the CVSS score of CVE-2026-65057?
CVE-2026-65057 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-65057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65057, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-65057

Explore →

Is Your Infrastructure Affected by CVE-2026-65057?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs