CVE-2026-5022: langflow · Missing Authorization
Affects langflowSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| langflow-ailangflow | Affected
| Fixed in– |
PyPIlangflow-ai/langflowpkg:pypi/langflow-ai/langflowOther threats | Affected
| Fixed in– |
GitHublangflowpkg:github/langflowOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-5022, organizations should immediately implement strict authentication and authorization controls on the '/api/v1/files/images/{flow_id}/{file_name}' endpoint. This includes verifying that the requester is authenticated and authorized to access the specific flow and image file. Employ role-based access control (RBAC) or attribute-based access control (ABAC) mechanisms to restrict access to image resources only to legitimate users. Additionally, consider implementing rate limiting and monitoring to detect and prevent enumeration attempts of flow IDs and file names. Review and sanitize file naming conventions to reduce predictability and exposure risk. Conduct a thorough audit of all API endpoints to ensure no other resources lack proper access controls. If possible, isolate sensitive image storage behind additional security layers or encrypt images at rest and in transit. Langflow developers should prioritize releasing a patch to enforce these controls by default. Organizations should also educate developers and administrators on secure API design principles to prevent similar issues. Finally, monitor network traffic for unusual access patterns to the vulnerable endpoint and respond promptly to any suspicious activity.
Description
The '/api/v1/files/images/{flow_id}/{file_name}' endpoint does not enforce any authentication or authorization checks, allowing any unauthenticated user to download images belonging to any flow by knowing (or guessing) the flow ID and file name.