CVE-2026-8446

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.5EG
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.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 contain an authentication bypass vulnerability in the Model Context Protocol (MCP) composer endpoint when mcp_composer_enabled=true (default) and projects are configured with auth_type=oauth .

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
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 is affected by security vulnerabilities in Model Context Protocol features

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 50× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 21:21 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-26 21:24 UTCEG score recompute
  5. 2026-08-26 14:47 UTCEPSS rescore
  6. 2026-08-25 22:08 UTCEG score recompute
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-24 23:45 UTCEG score recompute
  9. 2026-08-24 14:18 UTCEPSS rescore
  10. 2026-08-24 12:34 UTCEG score recompute
  11. 2026-08-23 03:00 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 04:26 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 06:02 UTCEG score recompute
  16. 2026-08-20 22:56 UTCEPSS rescore
  17. 2026-08-19 20:26 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 22:02 UTCEG score recompute
  20. 2026-08-18 13:49 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-17 23:39 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 01:17 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 25 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:55 UTCEG score recompute
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 04:33 UTCEG score recompute
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-14 06:09 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 20:36 UTCEG score recompute
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-11 22:15 UTCEG score recompute
  11. 2026-08-11 13:43 UTCEPSS rescore
  12. 2026-08-11 11:04 UTCEG score recompute
  13. 2026-08-11 00:00 UTCEPSS rescore
  14. 2026-08-09 14:20 UTCEG score recompute
  15. 2026-08-09 13:47 UTCEPSS rescore
  16. 2026-08-09 03:10 UTCEG score recompute
  17. 2026-08-08 16:37 UTCEPSS rescore
  18. 2026-08-07 17:37 UTCEG score recompute
  19. 2026-08-07 16:30 UTCEPSS rescore
  20. 2026-08-06 15:49 UTCEG score recompute
  21. 2026-08-06 13:47 UTCEPSS rescore
  22. 2026-08-05 18:31 UTCEG score recompute
  23. 2026-08-05 17:21 UTCEG score recompute
  24. 2026-08-05 16:51 UTCEG score recompute
  25. 2026-08-05 16:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-8446?
CVE-2026-8446 is a high vulnerability published on August 5, 2026. IBM Langflow OSS 1.0.0 through 1.10.3 contain an authentication bypass vulnerability in the Model Context Protocol (MCP) composer endpoint when mcpcomposerenabled=true (default) and projects are configured with auth_type=oauth .
When was CVE-2026-8446 disclosed?
CVE-2026-8446 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-8446 actively exploited?
CVE-2026-8446 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 79.5% of all scored CVEs.
What is the CVSS score of CVE-2026-8446?
CVE-2026-8446 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-8446?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8446, 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-8446

Explore →

Is Your Infrastructure Affected by CVE-2026-8446?

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

Start Free Scan →Browse All CVEs