CVE-2026-10129

HIGHPre-NVD 8.58.5
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.5Exploit: 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.3 contains a Server-Side Request Forgery (SSRF) protection bypass vulnerability in the API Request component. An authenticated attacker with low-level privileges (flow author role) can bypass SSRF protections by enabling the follow_redirects parameter and supplying a public URL that redirects to internal/localhost addresses. The vulnerability exists because the application validates only the initial URL but does not re-validate redirect destinations. This allows attackers to access internal HTTP services, localhost endpoints, cloud metadata services, and private network resources that should be unreachable when SSRF protection is enabled. Successful exploitation can lead to disclosure of sensitive information including credentials, tokens, internal API responses, and administrative panel data.

CVSS v3
8.5
EG Score
8.5(high)
EPSS
8.3%
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 via HTTP Redirect Following in Langflow API Request Component

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

Vendor Advisories for CVE-2026-10129(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 35× in last 7d / 35× 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-07 01:25 UTCEG score recompute
  2. 2026-07-07 01:25 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 13:59 UTCEG score recompute
  5. 2026-07-06 13:58 UTCGHSA enrichment
  6. 2026-07-06 02:31 UTCEG score recompute
  7. 2026-07-06 02:31 UTCGHSA enrichment
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 15:05 UTCEG score recompute
  10. 2026-07-05 15:04 UTCGHSA enrichment
  11. 2026-07-05 03:37 UTCEG score recompute
  12. 2026-07-05 03:37 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 16:08 UTCEG score recompute
  16. 2026-07-04 16:08 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 04:40 UTCEG score recompute
  19. 2026-07-04 04:40 UTCGHSA enrichment
  20. 2026-07-03 17:13 UTCEG score recompute
  21. 2026-07-03 17:13 UTCGHSA enrichment
  22. 2026-07-03 05:46 UTCEG score recompute
  23. 2026-07-03 05:46 UTCGHSA enrichment
  24. 2026-07-02 18:20 UTCEG score recompute
  25. 2026-07-02 18:19 UTCGHSA enrichment
Show 10 more
  1. 2026-07-02 06:53 UTCEG score recompute
  2. 2026-07-02 06:53 UTCGHSA enrichment
  3. 2026-07-01 19:27 UTCEG score recompute
  4. 2026-07-01 19:27 UTCGHSA enrichment
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 08:01 UTCEG score recompute
  8. 2026-07-01 08:01 UTCGHSA enrichment
  9. 2026-06-30 20:35 UTCEG score recompute
  10. 2026-06-30 20:33 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-10129?
CVE-2026-10129 is a high vulnerability published on June 30, 2026. IBM Langflow OSS 1.0.0 through 1.9.3 contains a Server-Side Request Forgery (SSRF) protection bypass vulnerability in the API Request component. An authenticated attacker with low-level privileges (flow author role) can bypass SSRF protections by enabling the follow_redirects parameter and…
When was CVE-2026-10129 disclosed?
CVE-2026-10129 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-10129 actively exploited?
CVE-2026-10129 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10129?
CVE-2026-10129 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-10129?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10129, 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-10129

Explore →

Is Your Infrastructure Affected by CVE-2026-10129?

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