CVE-2026-9196

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: 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 could allow an authenticated attacker to execute unintended code during Agentic Assistant validation due to improper handling of LLM‑generated components. The application executes model‑generated Python code in the backend during validation prior to user approval, which may allow an attacker to trigger side effects such as outbound network access, file system interaction, or data exfiltration with the privileges of the Langflow backend process.

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

Published

August 5, 2026

Last Modified

August 7, 2026

Advisory Details (1)

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

Security Bulletin: Langflow OSS is affected by arbitrary code execution in component generation, validation, and custom component handling

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

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

Frequently asked(5)

What is CVE-2026-9196?
CVE-2026-9196 is a high vulnerability published on August 5, 2026. IBM Langflow OSS 1.0.0 through 1.10.3 could allow an authenticated attacker to execute unintended code during Agentic Assistant validation due to improper handling of LLM‑generated components. The application executes model‑generated Python code in the backend during validation prior to user…
When was CVE-2026-9196 disclosed?
CVE-2026-9196 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9196 actively exploited?
CVE-2026-9196 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 78.1% of all scored CVEs.
What is the CVSS score of CVE-2026-9196?
CVE-2026-9196 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-9196?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9196, 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-9196

Explore →

Is Your Infrastructure Affected by CVE-2026-9196?

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