CVE-2026-7658

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-08-05. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: 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 does not properly validate the username field, allowing attackers to inject path traversal sequences and bypass containment checks. This enables multiple severe impacts, including arbitrary directory deletion, cross-tenant data destruction, and JWT signing key deletion leading to session invalidation.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
34(Track)
EG Risk 34/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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
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 arbitrary code execution in custom component validation and trusted code enforcement

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

Vendor Advisories for CVE-2026-7658(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 22× in last 7d / 47× 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 22:56 UTCEPSS rescore
  2. 2026-08-20 22:10 UTCGHSA enrichment
  3. 2026-08-19 21:57 UTCEG score recompute
  4. 2026-08-19 21:57 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 21:42 UTCEG score recompute
  7. 2026-08-18 21:42 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-17 21:23 UTCEG score recompute
  11. 2026-08-17 21:23 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 21:10 UTCEG score recompute
  14. 2026-08-16 21:10 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:15 UTCEPSS rescore
  18. 2026-08-15 20:57 UTCEG score recompute
  19. 2026-08-15 20:57 UTCGHSA enrichment
  20. 2026-08-15 01:31 UTCEPSS rescore
  21. 2026-08-14 20:44 UTCEG score recompute
  22. 2026-08-14 20:44 UTCGHSA enrichment
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-13 20:31 UTCGHSA enrichment
  25. 2026-08-12 20:19 UTCEG score recompute
Show 22 more
  1. 2026-08-12 20:19 UTCGHSA enrichment
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-11 20:06 UTCEG score recompute
  4. 2026-08-11 20:06 UTCGHSA enrichment
  5. 2026-08-11 13:43 UTCEPSS rescore
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-10 19:53 UTCGHSA enrichment
  8. 2026-08-09 19:40 UTCEG score recompute
  9. 2026-08-09 19:40 UTCGHSA enrichment
  10. 2026-08-09 13:47 UTCEPSS rescore
  11. 2026-08-08 19:28 UTCEG score recompute
  12. 2026-08-08 19:28 UTCGHSA enrichment
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-07 19:15 UTCEG score recompute
  15. 2026-08-07 19:15 UTCGHSA enrichment
  16. 2026-08-06 19:02 UTCGHSA enrichment
  17. 2026-08-06 15:48 UTCEG score recompute
  18. 2026-08-06 15:48 UTCGHSA enrichment
  19. 2026-08-06 13:47 UTCEPSS rescore
  20. 2026-08-05 19:30 UTCEG score recompute
  21. 2026-08-05 18:26 UTCEG score recompute
  22. 2026-08-05 18:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7658?
CVE-2026-7658 is a medium vulnerability published on August 5, 2026. IBM Langflow OSS 1.0.0 through 1.10.3 does not properly validate the username field, allowing attackers to inject path traversal sequences and bypass containment checks. This enables multiple severe impacts, including arbitrary directory deletion, cross-tenant data destruction, and JWT signing key…
When was CVE-2026-7658 disclosed?
CVE-2026-7658 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-7658 actively exploited?
CVE-2026-7658 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 73.4% of all scored CVEs.
What is the CVSS score of CVE-2026-7658?
CVE-2026-7658 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-7658?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7658, 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-7658

Explore →

Is Your Infrastructure Affected by CVE-2026-7658?

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

Start Free Scan →Browse All CVEs