CVE-2026-10564

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

IBM Langflow OSS 1.0.0 through 1.9.6 contains a Server-Side Request Forgery (SSRF). The legacy RSSReaderComponent in rss.py and SearXNG component in searxng.py make unvalidated HTTP requests to user-controlled URLs, bypassing SSRF protections introduced in version 1.9.3. An authenticated attacker can exploit this to access internal resources including cloud metadata services (AWS/Azure/GCP IMDS), potentially exfiltrating IAM credentials and enumerating internal networks. The vulnerability can also be triggered through prompt injection in agentic workflows due to tool_mode=True exposure.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
10.0%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

Security Bulletin: SSRF Vulnerability in Langflow OSS Legacy Components Bypasses Protection

https://www.ibm.com/support/pages/node/7277995

Vendor Advisories for CVE-2026-10564(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 9× in last 7d / 59× 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-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:04 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 19:49 UTCGHSA enrichment
  11. 2026-07-16 17:02 UTCEPSS rescore
  12. 2026-07-16 07:26 UTCGHSA enrichment
  13. 2026-07-15 19:05 UTCGHSA enrichment
  14. 2026-07-15 06:44 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 18:23 UTCGHSA enrichment
  17. 2026-07-14 06:02 UTCGHSA enrichment
  18. 2026-07-13 22:30 UTCEPSS rescore
  19. 2026-07-13 17:40 UTCGHSA enrichment
  20. 2026-07-13 06:12 UTCEPSS rescore
  21. 2026-07-13 05:19 UTCGHSA enrichment
  22. 2026-07-12 16:57 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-12 04:32 UTCGHSA enrichment
  25. 2026-07-11 16:11 UTCGHSA enrichment
Show 34 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 03:50 UTCGHSA enrichment
  3. 2026-07-10 15:29 UTCGHSA enrichment
  4. 2026-07-10 03:01 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 14:40 UTCGHSA enrichment
  7. 2026-07-09 02:17 UTCGHSA enrichment
  8. 2026-07-08 15:15 UTCEPSS rescore
  9. 2026-07-08 15:15 UTCEPSS rescore
  10. 2026-07-08 13:54 UTCGHSA enrichment
  11. 2026-07-08 01:32 UTCGHSA enrichment
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-07 13:11 UTCGHSA enrichment
  14. 2026-07-07 00:49 UTCGHSA enrichment
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 12:28 UTCGHSA enrichment
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 00:06 UTCGHSA enrichment
  19. 2026-07-05 11:43 UTCGHSA enrichment
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 23:22 UTCGHSA enrichment
  23. 2026-07-04 11:01 UTCGHSA enrichment
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-03 22:39 UTCGHSA enrichment
  26. 2026-07-03 10:19 UTCGHSA enrichment
  27. 2026-07-02 21:57 UTCGHSA enrichment
  28. 2026-07-02 09:36 UTCGHSA enrichment
  29. 2026-07-01 21:16 UTCGHSA enrichment
  30. 2026-07-01 15:06 UTCEPSS rescore
  31. 2026-07-01 15:06 UTCEPSS rescore
  32. 2026-07-01 08:56 UTCGHSA enrichment
  33. 2026-06-30 20:35 UTCEG score recompute
  34. 2026-06-30 20:33 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10564?
CVE-2026-10564 is a high vulnerability published on June 30, 2026. IBM Langflow OSS 1.0.0 through 1.9.6 contains a Server-Side Request Forgery (SSRF). The legacy RSSReaderComponent in rss.py and SearXNG component in searxng.py make unvalidated HTTP requests to user-controlled URLs, bypassing SSRF protections introduced in version 1.9.3. An authenticated attacker…
When was CVE-2026-10564 disclosed?
CVE-2026-10564 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10564 actively exploited?
CVE-2026-10564 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10564?
CVE-2026-10564 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-10564?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10564, 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-10564

Explore →

Is Your Infrastructure Affected by CVE-2026-10564?

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

Start Free Scan →Browse All CVEs