IBM Langflow OSS EUVD-2026-113149

Exploitation requires a valid authenticated session on the Langflow OSS instance (CVSS PR:L), limiting it to attackers who already have at least low-privilege access; it is not a remote-unauthenticated flaw. No user interaction is required (UI:N) and the vector is network-reachable (AV:N). The description does not name the specific endpoint, feature, or configuration that triggers the SSRF, so the exact trigger is not described in the available sources. Affected deployments are IBM Langflow OSS versions 1.0.0 through 1.12.3; the principal limiting factors are the authentication requirement and the confidentiality-only, low-magnitude impact (C:L, I:N, A:N).

This is a moderate-severity SSRF (CWE-918) with a vendor-assigned CVSS 3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). The signals are consistent and point to a limited, non-urgent issue rather than a top-priority emergency: the attack vector is network-based and complexity is low, but exploitation requires low-level authentication (PR:L), the scope is unchanged (S:U), and impact is confined to a low confidentiality loss with no integrity or availability impact (I:N/A:N). No EPSS score was supplied, so quantitative exploitation probability cannot be stated. The CVE is not listed in CISA KEV and no public exploit or PoC reference is provided, so there is no evidence of active exploitation. The vendor (IBM) is both the reporter and patch source, and the vuln.today priority 'this_month' aligns with a patch-when-convenient posture rather than act_now. Net: a real but lower-tier issue - an authenticated SSRF that can leak sensitive information, warranting patching within a normal cycle, not emergency response.

A remote attacker who already holds valid low-privilege credentials on an IBM Langflow OSS instance submits a request that coerces the server into making an attacker-controlled outbound request, returning sensitive information such as internal service responses or cloud metadata. Because the CVSS vector is AV:N/AC:L with low attack complexity, the request itself is straightforward once authenticated, but no public exploit code or PoC reference is provided and the trigger is not described in the available sources.