CVE-2026-79723

MEDIUMPre-NVD 5.05.0—
EchelonGraph scoreHIGH confidence

Score 5.0 from GitHub Security Advisory published 2026-09-11. a secondary CVSS source baseline 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.0Exploit: 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.11.5 could allow a remote authenticated attacker to obtain sensitive information due to improper validation of user-controlled API endpoints.

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

Published

September 10, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
No patch confirmed yet.
generic

Security Bulletin: Langflow is vulnerable to server-side request forgery due to missing egress validation on server-side URL fetches

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

Vendor Advisories for CVE-2026-79723(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 20× in last 7d / 34× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 18:17 UTCGHSA enrichment
  3. 2026-09-19 19:48 UTCEG score recompute
  4. 2026-09-19 19:48 UTCGHSA enrichment
  5. 2026-09-18 21:19 UTCEG score recompute
  6. 2026-09-18 21:19 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-17 22:00 UTCEG score recompute
  9. 2026-09-17 22:00 UTCGHSA enrichment
  10. 2026-09-16 23:31 UTCEG score recompute
  11. 2026-09-16 23:31 UTCGHSA enrichment
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 01:02 UTCGHSA enrichment
  15. 2026-09-15 09:04 UTCEG score recompute
  16. 2026-09-15 09:04 UTCGHSA enrichment
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-14 10:35 UTCEG score recompute
  20. 2026-09-14 10:35 UTCGHSA enrichment
  21. 2026-09-13 12:05 UTCEG score recompute
  22. 2026-09-13 12:05 UTCGHSA enrichment
  23. 2026-09-12 13:36 UTCGHSA enrichment
  24. 2026-09-11 15:07 UTCEG score recompute
  25. 2026-09-11 15:07 UTCGHSA enrichment
Show 9 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 14:23 UTCEG score recompute
  4. 2026-09-11 14:23 UTCGHSA enrichment
  5. 2026-09-11 13:50 UTCEG score recompute
  6. 2026-09-11 13:50 UTCGHSA enrichment
  7. 2026-09-10 22:19 UTCEG score recompute
  8. 2026-09-10 21:50 UTCEG score recompute
  9. 2026-09-10 21:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79723?
CVE-2026-79723 is a medium vulnerability published on September 10, 2026. IBM Langflow OSS 1.0.0 through 1.11.5 could allow a remote authenticated attacker to obtain sensitive information due to improper validation of user-controlled API endpoints.
When was CVE-2026-79723 disclosed?
CVE-2026-79723 was first published in the National Vulnerability Database on September 10, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-79723 actively exploited?
CVE-2026-79723 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 82.3% of all scored CVEs.
What is the CVSS score of CVE-2026-79723?
CVE-2026-79723 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-79723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-79723, 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-79723

Explore →

Is Your Infrastructure Affected by CVE-2026-79723?

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

Start Free Scan →Browse All CVEs