CVE-2026-10547 IBM CVE debrief

Who should care

Organizations using IBM Langflow OSS 1.0.0 through 1.10.3 should verify their inventory and assess the risk of exploitation. This includes reviewing system configurations, monitoring for suspicious activity, and implementing compensating controls to restrict access to the affected endpoint. Security teams should prioritize patching or mitigating this vulnerability to prevent potential security breaches.

Technical summary

IBM Langflow OSS 1.0.0 through 1.10.3 does not properly validate ownership in the deprecated POST /api/v1/build/{flow_id}/vertices endpoint, allowing an authenticated user to inject arbitrary graph data into a shared cache for any flow. This may result in cross-user cache pollution, unauthorized workflow execution, or denial of service. The vulnerability is due to inadequate validation of user input, which could lead to security issues if exploited.

Defensive priority

Authenticated users may inject arbitrary graph data into a shared cache, potentially causing cross-user cache pollution, unauthorized workflow execution, or denial of service. Organizations using IBM Langflow OSS 1.0.0 through 1.10.3 should verify their inventory and assess the risk of exploitation.

Recommended defensive actions

• Verify inventory of IBM Langflow OSS installations
• Assess the risk of exploitation
• Implement compensating controls to monitor and restrict access to the affected endpoint
• Review system configurations
• Monitor for suspicious activity
• Implement compensating controls to restrict access to the affected endpoint
• Track exceptions and retest remediated assets

Evidence notes

The CVE description indicates that IBM Langflow OSS 1.0.0 through 1.10.3 does not properly validate ownership in the deprecated POST /api/v1/build/{flow_id}/vertices endpoint. Limited evidence is available, and further verification is necessary to determine the full scope of the vulnerability. Organizations should verify their inventory and assess the risk of exploitation. Additional review of system logs and monitoring for suspicious activity may be necessary.

Official resources