Loading vulnerability…
Authenticated SSRF in IBM Langflow OSS
IBM Langflow OSS versions 1.0.0 through 1.12.3 contain a server-side request forgery vulnerability that allows an authenticated attacker to cause the application server to send unauthorized requests. Exploitation can enable enumeration of networks reachable from the server and facilitate further attacks. The affected function and request parameters are not specified.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An authenticated attacker can use the server's network access to issue unauthorized requests and potentially enumerate reachable services or networks. These requests may facilitate additional attacks against accessible systems. IBM assigns a CVSS v3.1 score of 4.3; arbitrary code execution or direct credential disclosure is not established for this vulnerability.
If you can’t patch tonight, do this now.
No vendor-provided workaround is identified. Interim risk-reduction measures include restricting application access to trusted users and limiting server-side outbound connectivity to required destinations, particularly blocking unnecessary access to internal services and cloud metadata endpoints. These controls do not replace upgrading.
Patch, then assume compromise.
Upgrade affected installations to Langflow OSS 1.12.4, as recommended by IBM. Back up the existing installation, review upgrade preparation instructions and release-specific configuration changes, and test workflows after upgrading.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.