CVE-2026-7646

Langflow MCP resource reads allowed encoded filename traversal

IBM / Langflow · Langflow OSS · MCP resources/read

First documented disclosure · Review checkpoint

Summary

An authenticated user could escape file storage using an encoded resource filename.

Severity and exploitation evidence

Medium · 6.5/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed sources document a weakness or controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

MCP decoded path separators after URI segmentation, then storage reads lacked the same containment validation used for writes.

Conditions required

An authenticated user can invoke MCP resources/read and the service can read a sensitive target file.

Potential impact

Disclosure of service-readable files; theft of signing secrets can enable account takeover in affected configurations.

Affected versions and configurations

IBM CNA/bulletin: 1.0.0 through 1.10.3. The later maintainer advisory identifies this specific encoded-filename path as corrected in Langflow 1.9.1 / backend 0.9.1.

Fix and mitigation status

IBM recommends 1.11.0 or later. The exact-path maintainer advisory and tagged source identify an earlier 1.9.1/backend 0.9.1 correction; the broader CNA range remains unresolved.

Practical next steps

Follow IBM’s 1.11.0-or-later recommendation and rotate secrets if exposed. Do not treat targeted-method evidence for 1.9.1 as a blanket clearance of all MCP paths.

Operating lesson

Decode before validation and enforce path ownership and containment at the storage boundary.

Evidence and limits

Public correction PR 12818 opened and merged April 21, predating the July 31 IBM bulletin, August 5 CNA publication and November 17 maintainer advisory. IBM assigns CVSS 3.1 6.5; the maintainer assigns 9.6, which is not substituted for the CNA score. The maintainer replay was method-level rather than a full HTTP/MCP deployment. Static review of the patch and tagged v1.9.1 confirms decoded-filename rejection, ownership checks and shared storage validation. The original reporter demonstrated secret theft/account takeover on 1.7.3; neither this review nor that result proves all later versions remain exploitable.

Sources