IBM Langflow OSS EUVD-2026-113141

Exploitation requires a valid authenticated account on a network-reachable IBM Langflow OSS instance (versions 1.0.0 through 1.12.3), per the PR:L / AV:N vector - it is not exploitable by a fully unauthenticated attacker. No user interaction is required (UI:N) and attack complexity is low (AC:L). The exact feature, endpoint, or flow component through which the OS command injection is reached is not described in the available sources, so the only confirmed limiting factor is the need for authenticated access and reachability of the instance; the fix is the vendor patch, which the evidence lists as available.

This is a credible near-term priority rather than a merely high-scoring theoretical issue. The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity flaw that needs only low-privilege authentication and no user interaction, yielding full confidentiality, integrity and availability impact - consistent with the arbitrary-code-execution outcome in the description. The vuln.today decision label is 'this_week', indicating elevated but not emergency urgency. No EPSS exploitation-probability score was supplied, the CVE is NOT listed in CISA KEV, and no public proof-of-concept or exploit reference is provided, so there is currently no public exploit identified at time of analysis and no evidence of active exploitation. The signals are internally consistent: a high-severity authenticated RCE with a vendor patch available but no confirmed in-the-wild activity. The single-source provenance (IBM self-reported, one IBM support reference) means EPSS and independent corroboration are missing - treat the severity as confirmed by the vendor-supplied vector while noting exploitation likelihood is unquantified.

An attacker who holds valid (even low-privilege) credentials for an internet-reachable IBM Langflow OSS instance submits input that is improperly neutralized and passed into an OS command, causing the server to execute attacker-chosen commands. Because the CVSS scope is unchanged with full C/I/A impact, this grants code execution in the context of the Langflow process on the host. No public exploit code is identified at time of analysis, and the specific vulnerable feature or endpoint is not described in the available sources.