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

Back
New CVE Detected

CVE-2026-7872 – Arbitrary File Read / Authentication Bypass – IBM Langflow OSS 1.0.0–1.10.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-7872 is a path traversal vulnerability (CWE-22) in IBM Langflow OSS versions 1.0.0 through 1.10.0, rated High (CVSS 7.5). By uploading a specially crafted tar archive, an attacker can read arbitrary files from the server — including the application’s JWT signing key — enabling complete authentication bypass through forged tokens for any user, including administrators. IBM has released version 1.10.1 to remediate the flaw.

Technical details

  • Root cause: A timing flaw in the symbolic link validation logic within the file component’s tar archive extraction. The application performs lexical resolution of symbolic link members before writing them to disk, allowing validation to pass while the subsequent extraction creates symlinks that point outside the intended directory (CWE-22: Improper Limitation of a Pathname to a Restricted Directory).
  • Trigger conditions: An attacker uploads a specially crafted tar archive containing embedded symbolic links targeting arbitrary paths on the server — for example, the application’s JWT secret key file.
  • Attack vector: Network-delivered over HTTP/HTTPS to the Langflow file upload endpoint. The CVSS vector records no required privileges and no user interaction; in practice, the authentication barrier is low given Langflow’s documented default configuration of AUTO_LOGIN enabled.
  • Impact: Successful exploitation grants read access to any file accessible to the application process. Extracting the JWT signing key allows forging valid authentication tokens for any user, including administrators, constituting a full authentication bypass. In Langflow’s architecture, administrative access further enables downstream remote code execution via Python code execution nodes.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.10.0

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade to Langflow OSS 1.10.1 or later, available via PyPI.
  • If immediate patching is not possible: Restrict network access to file upload endpoints at the firewall or reverse-proxy level, and rotate the application’s secret_key if filesystem exposure is suspected. IBM has not published an alternative workaround.

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