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

Back
New CVE Detected

CVE-2026-12942 – Directory Traversal / Arbitrary File Read – 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-12942 is a path traversal vulnerability (CWE-22) in IBM Langflow OSS versions 1.0.0 through 1.10.1, rated High severity (CVSS 7.5). An unauthenticated remote attacker can send specially crafted URL requests containing dot-dot sequences (/../) to unauthenticated API endpoints, enabling arbitrary file reads on the underlying server. IBM has released a patched version (1.10.2) and recommends immediate upgrade.

Technical details

  • Root cause: Insufficient validation and sanitization of user-supplied path parameters in exposed HTTP API endpoints, allowing directory traversal sequences to escape the intended file serving directory (CWE-22: Improper Limitation of a Pathname to a Restricted Directory).
  • Trigger conditions: No authentication or user interaction is required. An attacker only needs network access to the Langflow OSS web interface.
  • Attack vector: The attacker sends a crafted HTTP request containing /../ sequences in the URL path, directing the server to resolve file paths outside the application’s intended directory.
  • Impact: Successful exploitation allows an attacker to read arbitrary files from the server filesystem. This can expose sensitive data such as application configuration files, environment variable files containing API keys and database credentials, JWT signing secrets (enabling authentication token forgery), and other secrets stored on the host.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.1 (inclusive)

Severity

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

Mitigation and recommended actions

  • Immediate action: Upgrade IBM Langflow OSS to version 1.10.2, available via PyPI.
  • If immediate patching is not possible: Restrict network access to Langflow OSS instances using firewall rules or network segmentation to prevent unauthenticated internet-facing exposure. IBM has not documented any in-application workarounds for this vulnerability.

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