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

Back
New CVE Detected

CVE-2026-13448 – Unauthenticated RCE via Incomplete Denylist – IBM Langflow OSS 1.0.0–1.10.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-13448 is a high-severity unauthenticated remote code execution (RCE) vulnerability affecting IBM Langflow OSS versions 1.0.0 through 1.10.1. The flaw exists in the public flow build endpoint and allows a network-based attacker with no credentials to execute arbitrary code on the server. IBM has assigned a CVSS v3.1 base score of 8.1 (High) and recommends immediate upgrade to version 1.10.2.

Technical details

  • Root cause: An incomplete denylist in the validate_public_flow_no_code_execution() function fails to restrict several code-execution-capable agent components — specifically OpenDsStarAgent, CodeActAgentSmolagents, and CSVAgent. These components can be invoked through the public flow build endpoint without being blocked by the intended security control.
  • Trigger condition: The vulnerable endpoint (/api/v1/build_public_tmp/{flow_id}/flow) is accessible without authentication for flows configured with the PUBLIC access type. An attacker who can identify or enumerate a PUBLIC flow ID can submit a crafted request embedding one of the unblocked agent components to trigger code execution.
  • Attack vector: Network-delivered over HTTP/HTTPS; no authentication, no user interaction required. The AC:H (High Complexity) designation reflects that exploitation requires the targeted flow to be set to PUBLIC access type.
  • Impact: Full remote code execution on the server with high impact to confidentiality, integrity, and availability (C:H/I:H/A:H). A successful exploit can result in data exfiltration, credential theft, and complete server compromise.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.1 (inclusive)

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate action: Upgrade to Langflow OSS 1.10.2 or later, available via PyPI. IBM has confirmed this version contains the fix.
  • No workarounds available: IBM’s security bulletin does not document any configuration-level mitigations. Until patching is complete, consider restricting network access to the Langflow instance and auditing which flows have been set to PUBLIC access type.
  • Review and audit any flows currently configured as PUBLIC to assess potential exposure prior to patching.

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