CVE-2026-104315
Langflow authenticated request forgery enables network probing
IBM / Langflow · Langflow OSS
First documented disclosure · Review checkpoint
Summary
Network enumeration and possible follow-on access; a completed compromise is not established.
Severity and exploitation evidence
Medium · 4.3/10 · CVSS 3.1. Severity source.
Exploitation not established: The reviewed primary records do not establish malicious exploitation or a confirmed victim.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The application sends unauthorized server-side requests from an attacker-influenced path; the exact component is undisclosed.
Conditions required
An authenticated user can invoke the affected request feature.
Potential impact
Network enumeration and possible follow-on access; a completed compromise is not established.
Affected versions and configurations
IBM lists Langflow OSS 1.0.0 through 1.12.3.
Fix and mitigation status
1.12.4 per IBM; this is an issue-specific fix, not assurance that the old release addresses later findings.
Practical next steps
Upgrade to a current supported release containing the fix; back up the deployment and validate workflow behavior.
Operating lesson
Restrict connector destinations and isolate internal services from application egress.
Evidence and limits
IBM bulletin 7293015 was initially published 2026-10-19; the CNA record followed on 2026-10-29. Earlier upstream patches are not assigned to this CVE by inference. Exact technical details absent from the public record remain unknown; a CVSS score is not an observed incident.
Sources
- IBM published CNA and issue-specific remediation
Primary source ·
- IBM full product security bulletin
Primary source ·