What is the CVSS score of CVE-2026-7787?

CVE-2026-7787 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of IBM Langflow OSS are affected by CVE-2026-7787?

Organizations using IBM Langflow OSS versions 1.0.0-1.9.1 face unauthorized data access and modification risks: authenticated users can view and modify other users' sensitive data, compromising…. A patch is available.

How to fix or mitigate CVE-2026-7787?

24 hours: Inventory all IBM Langflow OSS instances running versions 1.0.0-1.9.1 and identify which systems process sensitive or regulated data. 7 days: Obtain and test the vendor patch in a staging environment, then deploy to production beginning with systems handling sensitive data. 30 days: Confirm all affected IBM Langflow OSS instances have been upgraded to the patched version and audit access logs for evidence of unauthorized data access attempts.

IBM Langflow OSS CVE-2026-7787

EUVD-2026-36251 HIGH

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-06-11 ibm

GHSA-gfrh-qj3c-qwrr

Authentication Bypass IBM Langflow Oss

8.1

CVSS 3.1 · NVD

Severity by source

Vendor (ibm) PRIMARY

HIGH

qualitative

NVD

8.1 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

vuln.today AI

8.1 HIGH

Network-reachable API, low complexity, requires any authenticated account (PR:L), no UI; IDOR enables reading and modifying other users' sensitive objects (C:H/I:H) but no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Analysis Updated

Jun 16, 2026 - 15:13 vuln.today

v3 (cvss_changed)

Analysis Updated

Jun 16, 2026 - 15:13 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jun 16, 2026 - 15:07 vuln.today

cvss_changed

CVSS changed

Jun 16, 2026 - 15:07 NVD

7.5 (HIGH) 8.1 (HIGH)

Analysis Generated

Jun 11, 2026 - 15:46 vuln.today

DescriptionNVD

IBM Langflow OSS 1.0.0 through 1.9.1 could allow an authenticated user to read or modify sensitive information by bypassing authentication using insecure direct object references.

AnalysisAI

Insecure direct object reference (IDOR) in IBM Langflow OSS 1.0.0 through 1.9.1 allows an authenticated user to read or modify sensitive resources belonging to other users by manipulating object identifiers. The flaw carries a CVSS 8.1 (High) rating due to high confidentiality and integrity impact over the network, though EPSS exploitation probability remains low at 0.04% and there is no public exploit identified at time of analysis. SSVC classifies exploitation as 'none' but flags the issue as automatable with partial technical impact, indicating defenders should still prioritize patching given the trivial attack complexity.

Technical ContextAI

Langflow OSS is IBM's open-source low-code framework for building LLM-powered agent and workflow applications, exposing a web API and UI for orchestrating chains, components, and flows. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): endpoints accept object identifiers from the authenticated client but fail to verify that the calling user owns or has rights to the referenced object, so changing an ID in a request URL or body grants access to another tenant's data. The affected CPE cpe:2.3:a:ibm:langflow_oss covers all builds in the 1.0.0-1.9.1 range, which corresponds to the period before IBM hardened object-level authorization checks in the request handlers.

RemediationAI

Apply the patch available per IBM's vendor advisory at https://www.ibm.com/support/pages/node/7275453, which addresses the IDOR by enforcing per-object authorization checks; upgrade beyond Langflow OSS 1.9.1 to the fixed build identified in that bulletin. Until the upgrade is in place, restrict Langflow access to a small set of trusted authenticated users (the bug requires a valid account, so removing low-trust accounts immediately reduces exposure), put the application behind an authenticated reverse proxy or VPN to prevent broad internet access, and review web/access logs for sequential or enumerated object IDs in API paths - accepting that proxy and logging controls do not stop a legitimate but malicious user from abusing IDs they can already reach. If you self-host with custom integrations, audit any code that consumes Langflow object identifiers to ensure downstream services do not cache or trust cross-tenant references.