CVE-2026-55446: Langflow Unauthenticated Denial of Service via Malformed File Upload
Langflow versions prior to 1.0.19 contain a denial-of-service vulnerability in the file upload endpoint. An attacker can submit a specially crafted upload request with an extremely long multipart form boundary—without needing to authenticate—causing the application to become unresponsive and unusable for all legitimate users. The impact persists until the service is restarted or manually recovered.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-400
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-23 / 2026-06-24
NVD description (verbatim)
Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to 1.0.19, an attacker can send a /api/v1/files/upload/ request without any authentication token/cookies and abuse a very long multipart form boundary to make the langflow app unusable for all users for an indefinite amount of time. This vulnerability is fixed in 1.0.19.
3 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-55446 is a resource exhaustion vulnerability (CWE-400) affecting Langflow's /api/v1/files/upload/ endpoint. The flaw allows unauthenticated attackers to send HTTP POST requests with abnormally long multipart form boundaries in the Content-Type header. This triggers inefficient parsing or buffer handling within the application, exhausting system resources and rendering the service unavailable. The vulnerability requires no special privileges, no user interaction, and is trivial to trigger over the network.
Business impact
This vulnerability enables attackers to launch denial-of-service attacks against Langflow deployments with minimal effort. Organizations relying on Langflow for AI workflow orchestration face service disruption, operational downtime, and potential SLA violations. The unauthenticated nature means attackers do not need insider access or compromised credentials. In production environments supporting critical automation tasks, repeated attacks could severely degrade business continuity.
Affected systems
Langflow versions prior to 1.0.19 are affected. The vulnerability is resolved in version 1.0.19 and later. Both self-hosted and cloud-hosted Langflow instances are at risk if running vulnerable versions.
Exploitability
This vulnerability has high exploitability. The attack requires only network access to the affected endpoint and can be executed by any unauthenticated user. No sophisticated tools, credentials, or user interaction are required. An attacker can trivially automate repeated requests to maintain service degradation. The low complexity and public nature of REST APIs make this a practical attack vector.
Remediation
Upgrade Langflow to version 1.0.19 or later to patch this vulnerability. Organizations should prioritize this upgrade to eliminate the unauthenticated DoS exposure. Verify the upgrade is successful by testing file upload functionality post-deployment.
Patch guidance
Apply the upgrade to Langflow 1.0.19 or later according to your deployment method (container, package manager, or manual installation). Review the official Langflow release notes for version 1.0.19 to confirm this fix is included and to identify any breaking changes or migration steps. Test uploads in a staging environment before production deployment.
Detection guidance
Monitor for unusual patterns of requests to /api/v1/files/upload/ from unexpected sources or at high frequency. Log and alert on requests with abnormally long Content-Type headers or malformed multipart boundaries. Network intrusion detection systems (IDS) may identify such requests through payload analysis. If you suspect active exploitation, check application logs for failed or hung upload requests coinciding with service degradation.
Why prioritize this
This vulnerability merits immediate attention despite not being on the KEV catalog. The combination of unauthenticated access, network reachability, trivial exploitability, and severe impact (complete service unavailability) creates a high-priority risk. Organizations should treat this as urgent if they operate Langflow in production or expose it to untrusted networks.
Risk score, explained
The CVSS 3.1 score of 7.5 (HIGH) reflects the severity of the impact: availability is completely compromised (A:H), the attack is network-based (AV:N), requires no authentication (PR:N), and no user interaction (UI:N). The score appropriately captures the serious operational risk, though the lack of confidentiality or integrity impact prevents a critical rating.
Frequently asked questions
Can this vulnerability be exploited from the internet, or only from internal networks?
This vulnerability can be exploited from any network with access to the affected Langflow instance. Since no authentication is required, an attacker on the internet can trigger the DoS if the upload endpoint is reachable. Organizations should use network controls (firewalls, VPNs, IP allowlists) to restrict access to Langflow APIs if they are exposed to untrusted networks.
Does upgrading to 1.0.19 require downtime or configuration changes?
Verify the official Langflow documentation for version 1.0.19 to confirm any downtime requirements or migration steps. Most patch upgrades are intended to be non-breaking, but it is best practice to test the upgrade in a staging environment first.
What should we do if we suspect this vulnerability has been exploited in our environment?
Check application logs and request logs for unusual patterns around the /api/v1/files/upload/ endpoint. Look for requests with abnormally long or malformed multipart boundaries. If you identify suspicious activity, isolate the affected Langflow instance, review system resource usage at the time of the incident, and then apply the upgrade to 1.0.19.
If we have rate limiting or WAF rules in place, does that fully protect us?
Rate limiting and WAF rules may reduce the impact by slowing repeated exploitation, but they do not fully prevent this vulnerability. A determined attacker can still craft a single malicious request to cause degradation. The only complete mitigation is to upgrade to version 1.0.19.
This analysis is based on the published CVE record as of June 2026. Security teams should independently verify patch availability, version numbers, and compatibility with their deployments against official vendor advisories. This summary is for informational purposes and does not constitute professional security advice. Always test patches in non-production environments before deployment. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2023-54365HIGHTraefik HTTP/2 Denial of Service Vulnerability – Rapid Reset Attack
- CVE-2024-14036HIGHDräger Core Denial of Service via Malformed SDC Messages
- CVE-2025-52293HIGHGPAC MP4Box HEVC Parser Denial of Service (CVSS 7.5)
- CVE-2025-53114HIGHCometD Denial-of-Service via Unacknowledged Message Queue Overflow
- CVE-2025-61025HIGHOpenLink Virtuoso 7.2.11 Remote DoS via SQL Query Parsing
- CVE-2026-10069HIGHShibby Tomato miniupnpd Resource Exhaustion Vulnerability
- CVE-2026-10143HIGHkafka-python SCRAM DoS – Event Loop Freeze Vulnerability
- CVE-2026-12151HIGHundici WebSocket Memory Exhaustion DoS Vulnerability