CVE-2026-9081

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 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.10.3, and 1.0.0 through 1.10.3 contains a Server-Side Request Forgery (SSRF) vulnerability in the validate_model_provider_key() function for the Ollama provider. The function accepts a user-supplied OLLAMA_BASE_URL parameter and passes it directly to requests.get() without validation, scheme/host allowlisting, or filtering of private IP ranges (loopback, RFC1918, link-local addresses).

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 6, 2026

Advisory Details (1)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

Security Bulletin: Langflow OSS is affected by server-side request forgery in provider validation and API request functionality

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9081?
CVE-2026-9081 is a high vulnerability published on August 5, 2026. IBM Langflow OSS 1.0.0 through 1.10.3, and 1.0.0 through 1.10.3 contains a Server-Side Request Forgery (SSRF) vulnerability in the validatemodelproviderkey() function for the Ollama provider. The function accepts a user-supplied OLLAMABASE_URL parameter and passes it directly to requests.get()…
When was CVE-2026-9081 disclosed?
CVE-2026-9081 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9081 actively exploited?
CVE-2026-9081 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 93.1% of all scored CVEs.
What is the CVSS score of CVE-2026-9081?
CVE-2026-9081 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-9081?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9081, 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-9081

Explore →

Is Your Infrastructure Affected by CVE-2026-9081?

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

Start Free Scan →Browse All CVEs