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

Back
New CVE Detected

CVE-2026-7787 – Unauthenticated IDOR / Sensitive Data Disclosure – IBM Langflow OSS 1.0.0–1.9.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-7787 is a high-severity Insecure Direct Object Reference (IDOR) vulnerability — classified as CWE-639 (Authorization Bypass Through User-Controlled Key) — affecting IBM Langflow OSS versions 1.0.0 through 1.9.1. The flaw allows unauthenticated, network-accessible attackers to retrieve other users’ sensitive session data, including chat history, by supplying attacker-controlled session identifiers to a public API endpoint. IBM has assigned a CVSS v3.1 base score of 7.5 (High) and released a patch in Langflow OSS version 1.9.2.

Technical details

  • Root cause: The POST endpoint /api/v1/build_public_tmp/{flow_id}/flow — used for executing publicly shared flows — fails to enforce session namespace isolation. When a public flow contains a Memory component with an empty session_id field, the component accepts and processes the caller-supplied session_id value without validation or ownership checks.
  • Trigger conditions: The vulnerable path is reachable unauthenticated. An attacker only needs a target flow’s flow_id, which is exposed as a UUID in Langflow’s shareable flow URLs.
  • Attack vector: Remote, over the network, requiring no authentication and no user interaction. Attack complexity is low.
  • Impact: An attacker can supply predictable or enumerated session IDs to read conversation history and other sensitive data stored in Memory components belonging to other users’ sessions, resulting in a high-confidentiality-impact breach. The CVE description also notes the potential to modify sensitive information, making integrity impact a risk factor in certain configurations.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.9.1 (inclusive)

Severity

| Metric | Value |
|—|—|
| 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 |
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Confidentiality Impact | High |

Mitigation and recommended actions

  • Immediate action — patch: Upgrade to IBM Langflow OSS version 1.9.2 or later, available via PyPI. This is the only documented remediation; IBM lists no workarounds for this vulnerability.
  • Network mitigation (if patching is not immediately possible): Restrict external network access to Langflow instances. Avoid exposing Langflow deployments directly to the public internet. Apply firewall rules or reverse-proxy access controls to limit reachability of the /api/v1/build_public_tmp/ endpoint to trusted networks only.
  • Review public flow configurations: Audit all deployed flows using Memory components with empty session_id fields, as these configurations are directly exploitable through the vulnerable endpoint.

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