PatchSiren cyber security CVE debrief
CVE-2026-10700 IBM CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-30T19:17:02.100Z and has not been modified since then. The NVD entry is currently Undergoing Analysis. IBM Langflow OSS 1.0.0 through 1.8.4 contains multiple broken access control vulnerabilities in its file handling API. The /api/v1/files/images/{flow_id}/{file_name} endpoint does not enforce authentication or authorization checks, allowing unauthenticated remote attackers to retrieve image files associated with any flow by specifying a valid flow_id and file_name. Additionally, the /api/v1/files/download/{flow_id}/{file_name} endpoint requires authentication but fails to properly validate ownership of the requested resource, allowing authenticated users to access files belonging to other users by supplying arbitrary identifiers, leading to an authorization bypass (IDOR). Successful exploitation may result in unauthorized disclosure of sensitive data, including files stored in private flows. This issue breaks tenant isolation in multi-user deployments. Users of IBM Langflow OSS, especially those with multi-user deployments, should be aware of this vulnerability and take defensive actions to prevent unauthorized access to sensitive data. Medium-priority defensive actions are recommended due to the potential for unauthorized disclosure of sensitive data in multi-user deployments of IBM Langflow OSS. Evidence from the NVD and IBM support pages indicates that IBM Langflow OSS contains broken access control vulnerabilities in its file handling API. The /api/v1/files/images/{flow_id}/{file_name} endpoint lacks authentication and authorization checks, while the /api/v1/files/download/{flow_id}/{file_name} endpoint fails to validate resource ownership properly.
- Vendor
- IBM
- Product
- Langflow OSS
- CVSS
- MEDIUM 6.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-30
- Original CVE updated
- 2026-07-31
- Advisory published
- 2026-07-30
- Advisory updated
- 2026-07-31
Who should care
Users of IBM Langflow OSS, especially those with multi-user deployments, should be aware of this vulnerability and take defensive actions to prevent unauthorized access to sensitive data.
Technical summary
IBM Langflow OSS 1.0.0 through 1.8.4 contains multiple broken access control vulnerabilities in its file handling API. The /api/v1/files/images/{flow_id}/{file_name} endpoint does not enforce authentication or authorization checks, allowing unauthenticated remote attackers to retrieve image files associated with any flow. The /api/v1/files/download/{flow_id}/{file_name} endpoint requires authentication but fails to properly validate ownership of the requested resource, allowing authenticated users to access files belonging to other users.
Defensive priority
Medium-priority defensive actions are recommended due to the potential for unauthorized disclosure of sensitive data in multi-user deployments of IBM Langflow OSS.
Recommended defensive actions
- Implement authentication and authorization checks for the /api/v1/files/images/{flow_id}/{file_name} endpoint
- Enhance validation of resource ownership for the /api/v1/files/download/{flow_id}/{file_name} endpoint
- Enforce tenant isolation in multi-user deployments
- Monitor for unauthorized access attempts to user files
- Apply vendor-provided patches or updates
Evidence notes
Evidence from the NVD and IBM support pages indicates that IBM Langflow OSS contains broken access control vulnerabilities in its file handling API. The /api/v1/files/images/{flow_id}/{file_name} endpoint lacks authentication and authorization checks, while the /api/v1/files/download/{flow_id}/{file_name} endpoint fails to validate resource ownership properly.
Official resources
-
CVE-2026-10700 CVE record
CVE.org
-
CVE-2026-10700 NVD detail
NVD
-
Source item URL
nvd_modified
- Source reference
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-30T19:17:02.100Z and has not been modified since then.