IBM Langflow OSS EUVD-2026-113153

Exploitation requires an existing authenticated account on the Langflow OSS instance (CVSS PR:L confirms authentication is needed; this is not an unauthenticated attack despite the 'Authentication Bypass' tag). The attacker must be able to reach the application over the network (AV:N) and no user interaction is required (UI:N). The flaw is an improper-access-control issue (CWE-284) permitting arbitrary SQL command execution; the specific feature, endpoint, or configuration that exposes it is not described in the available sources. Limiting factors: the requirement for valid credentials substantially narrows exposure to deployments with multiple, shared, or untrusted authenticated users, and affected versions are bounded to 1.0.0 through 1.12.3, so patched or newer instances are not at risk.

This is a genuinely high-severity, serious-but-not-emergency issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity flaw requiring only low-level authentication, with high impact to confidentiality, integrity, and availability - consistent with an authenticated user being able to run arbitrary SQL. However, the exploitation signals temper the raw 8.8: CISA SSVC reports Exploitation=none (no observed exploitation), Automatable=no, and Technical Impact=partial, and the vuln.today Decision label is 'this_week' rather than act_now/emergency. There is no CISA KEV listing and no public exploit or PoC reference in the supplied data, so this is not confirmed as actively exploited. The combination points to a real, patch-this-week priority for anyone running Langflow OSS with multiple or untrusted authenticated users, but not a drop-everything mass-exploitation event. Note one tension to verify: the input Tags include 'Authentication Bypass', yet both the description (CWE-284 improper access control, remote AUTHENTICATED attacker) and the CVSS PR:L indicate the attacker must already be authenticated - this is a privilege/access-control flaw for logged-in users, not an unauthenticated bypass; treat the 'Authentication Bypass' label with caution.

A remote attacker who already holds a low-privileged authenticated account on a Langflow OSS instance (versions 1.0.0 through 1.12.3) abuses improper access control to issue arbitrary SQL commands against the backend database. Given AC:L and no required user interaction, the request can be sent directly once authenticated, potentially allowing the attacker to read, modify, or destroy data beyond their authorization. No public exploit or PoC reference is present in the available data, and the specific vulnerable endpoint or mechanism is not described in the supplied sources.