Skip to main content
VulnerabilityPublished Updated

CVE-2026-9130: IBM Langflow OSS · Insecure Direct Object Reference

Affects IBM Langflow OSSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
IBMLangflow OSSAffected
  • >=1.0.0 <=1.10.3
Fixed in–

CPE configurations (2)

  • cpe:2.3:a:ibm:langflow_oss:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:langflow_oss:1.10.3:*:*:*:*:*:*:*

AI-suggested

Until a fix is available, consider reviewing deployment configurations, especially the LANGFLOW_AUTO_LOGIN setting, and restrict access to trusted users. Monitor vendor communications for official patches or updates.

Description

IBM Langflow OSS 1.0.0 through 1.10.3 contain an authorization bypass vulnerability in the MemoryComponent that allows authenticated users to access chat history of other users via session_id collision. The MemoryComponent.retrieve_messages and store_message methods filter on session_id without validating flow_id or user_id ownership, enabling cross-user information disclosure through multiple authenticated API endpoints including /api/v1/run/*, /api/v1/responses, and /api/v2/workflow/*. This vulnerability only affects multi-user deployments with LANGFLOW_AUTO_LOGIN=False.

References

Community reviews

Loading reviews…