CVE-2026-7663
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Langflow OSS 1.0.0 through 1.9.6 could allow unauthenticated attackers to access protected MCP project resources and execute MCP operations due to improper authorization enforcement in the Streamable MCP transport endpoint.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM Langflow OSS versions 1.0.0 through 1.9.6 fail to enforce authorization checks on the Streamable MCP transport endpoint, allowing unauthenticated attackers to bypass access controls and access protected MCP project resources or execute arbitrary MCP operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0.0, < 1.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Langflow versionQuery the Langflow service for its version (e.g., via API endpoint, package manager, or service banner) or inspect the installed package versionAffected if version is 1.0.0 through 1.9.6 inclusive
-
Verify MCP Streamable transport is in useInspect Langflow configuration for MCP-related settings, or check for running MCP server processes/endpoints that use Streamable transportAffected if MCP Streamable transport endpoint is enabled or configured
-
Assess network exposure of MCP endpointsReview firewall rules, reverse proxy configuration, or network ACLs to determine if MCP endpoints are accessible from untrusted networksAffected if MCP endpoints are reachable without authentication from external or untrusted sources
-
Confirm authorization is bypassedAttempt a test request to the MCP Streamable transport endpoint without valid credentials and observe if the request is processed without authorization failureAffected if unauthenticated requests to MCP endpoints succeed when they should require authorization
You are affected if Langflow version is 1.0.0 through 1.9.6 AND the MCP Streamable transport endpoint is exposed and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.10.0
Upgrade IBM Langflow to a version beyond 1.9.6 where proper authorization enforcement is implemented. If immediate upgrade is not feasible, restrict network access to MCP endpoints via firewall or reverse proxy rules.
1.10.0
- Upgrade Langflow to version 1.10.0 or later to resolve the improper authorization vulnerability
- After upgrading, verify that MCP project resources require proper authentication
- Confirm that the Streamable MCP transport endpoint now enforces authorization checks for all protected resources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7663 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data