Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-10560 – Missing Authentication / Information Disclosure – IBM Langflow OSS 1.0.0–1.9.6

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-10560 is a missing authentication vulnerability (CWE-287) in IBM Langflow OSS versions 1.0.0 through 1.9.6, carrying a CVSS v3.1 base score of 8.2 (High). The flaw affects the /api/v1/build_public_tmp/ API endpoint family, allowing unauthenticated, network-accessible attackers to read sensitive build event data or cancel in-flight build jobs without any credentials or user interaction. With thousands of Langflow instances directly exposed to the internet, this vulnerability poses a significant risk of sensitive data leakage to any organization running an unpatched deployment.

Technical details

  • Root cause: Missing authentication controls (CWE-287 – Improper Authentication) on two endpoints within the /api/v1/build_public_tmp/ family; the endpoints perform no authentication checks and no access control validation on incoming requests.
  • Affected endpoints:
    • GET /api/v1/build_public_tmp/{job_id}/events — streams live build event data, which can include customer prompts, LLM responses, API keys, internal documents from RAG pipelines, and server-side Python tracebacks.
    • POST /api/v1/build_public_tmp/{job_id}/cancel — cancels in-flight build jobs, enabling disruption of workflow execution.
  • Trigger conditions: Exploitation requires only a valid job identifier; no authentication token or privileged account is needed. The identifier can be obtained through reconnaissance or enumeration.
  • Attack vector: Fully network-accessible with no privileges required and no user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: High confidentiality impact through unauthorized exposure of sensitive build event data; low integrity impact through unauthorized cancellation of running jobs.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.9.6

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
  • CWE: CWE-287 – Improper Authentication

Mitigation and recommended actions

  • Immediate action: Upgrade to IBM Langflow OSS version 1.10.0, which contains the vendor-provided fix. The patched package is available at pypi.org/project/langflow/.
  • No workarounds identified: IBM has not published alternative mitigations for this vulnerability. Organizations unable to patch immediately should restrict network access to Langflow instances and block unauthenticated external access to the /api/v1/build_public_tmp/ endpoint family at the network or reverse-proxy layer as a temporary defensive measure.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge