What is the CVSS score of EUVD-2026-51243?

EUVD-2026-51243 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.4%.

Which versions of IBM Langflow OSS are affected by EUVD-2026-51243?

Unauthenticated attackers can remotely read arbitrary files from systems running IBM Langflow OSS versions 1.0.0-1.10.1, creating immediate risk of exposure for confidential configuration, API keys,…. A patch is available.

How to fix or mitigate EUVD-2026-51243?

Within 24 hours, inventory all IBM Langflow OSS deployments running versions 1.0.0 through 1.10.1, prioritizing publicly accessible instances and noting any storage of secrets or configuration files. Within 7 days, upgrade all identified systems to the patched version released by IBM and verify successful deployment; as interim mitigation, restrict network access to Langflow or configure web server rules to block requests containing directory-traversal sequences (../) if patching cannot be completed immediately. Within 30 days, verify patching of all remaining systems, audit server logs for exploitation attempts spanning the exposure window, and conduct credential rotation for any secrets that may have been stored in accessible configuration directories or environment files.

IBM Langflow OSS EUVD-2026-51243

| CVE-2026-12942 HIGH

Path Traversal (CWE-22)

2026-07-30 ibm

GHSA-rmxx-p7v6-pmfp

Path Traversal IBM Langflow Oss

7.5

CVSS 3.1 · NVD

Severity by source

Vendor (ibm) PRIMARY

HIGH

qualitative

NVD

7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

vuln.today AI

7.5 HIGH

Remote unauthenticated URL-based traversal with no user interaction (AV:N/AC:L/PR:N/UI:N); file-read only yields high confidentiality but no integrity or availability impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 30, 2026 - 17:53 vuln.today

CVE Published

Jul 30, 2026 - 16:45 cve.org

HIGH 7.5

DescriptionNVD

IBM Langflow OSS 1.0.0 through 1.10.1 could allow a remote attacker to traverse directories on the system. An attacker could send a specially crafted URL request containing "dot dot " sequences ( /.. /) to view arbitrary files on the system.

AnalysisAI

Arbitrary file read in IBM Langflow OSS versions 1.0.0 through 1.10.1 allows remote unauthenticated attackers to retrieve files outside the intended web root by submitting URLs containing directory-traversal ("../") sequences. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, exploitation needs no authentication or user interaction and can expose sensitive files such as configuration, secrets, or source code. No public exploit identified at time of analysis, and there is no indication of active exploitation.

Technical ContextAI

IBM Langflow OSS is an open-source, Python-based low-code framework for visually building LangChain/LLM agent workflows, exposing a web UI and REST API. The flaw is a classic CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal): a request parameter or URL path used to locate a file on disk is not properly canonicalized or restricted, so "dot dot slash" sequences (/../) walk above the intended base directory. The affected component is identified by CPE cpe:2.3:a:ibm:langflow_oss, and the impact profile (C:H/I:N/A:N) indicates the traversal permits reading arbitrary files but not writing to them or degrading availability.

RemediationAI

Patch available per vendor advisory: upgrade IBM Langflow OSS to the fixed release referenced in IBM's advisory at https://www.ibm.com/support/pages/node/7279993 (the exact patched version is not stated in the provided data and must be taken from that advisory). Until patching is possible, reduce exposure by placing the Langflow web interface behind authentication and network restrictions so it is not reachable from untrusted networks, and add a reverse proxy or WAF rule to block requests whose paths contain traversal sequences (../, encoded variants like %2e%2e) - noting that URL-decoding and normalization must be handled carefully to avoid bypasses and that overly strict rules could break legitimate file-serving routes. Avoid running the service as a privileged user so a successful read is limited to files that account can access.