dbcve.org
LangflowApplication

CVE-2026-7787

HIGH · 8.1 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 1.9.2 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Langflow OSS versions 1.0.0 through 1.9.1 contains an Insecure Direct Object Reference (IDOR) vulnerability that allows authenticated users to bypass proper authorization checks and access or modify sensitive data by manipulating direct object references (such as database IDs or file paths) in API requests.

MitigationImplement proper authorization checks on all endpoints that handle sensitive objects, ensuring users can only access resources they are explicitly authorized for. Consider implementing indirect object references and role-based access control (RBAC).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LangflowApplication
Affected:>= 1.0.0, < 1.9.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Langflow version
    Run 'pip show langflow' or check the running service's version endpoint (e.g., /api/v1/version or /api/version)
    Affected if The installed version is 1.0.0 through 1.9.1 (anything >= 1.0.0 and < 1.9.2)
  2. Verify API authentication is enabled
    Review Langflow configuration files (config.yaml, .env) or check if the /api endpoints require authentication tokens
    Affected if API authentication is disabled or optional, making the IDOR accessible to unauthenticated users (though CVE states authenticated users, authentication being present is a prerequisite)
  3. Inspect API endpoints for object reference handling
    Review API route handlers (typically in api/ or routes/ directories) that accept object IDs in URLs (e.g., /api/flows/{flow_id}, /api/run/{run_id})
    Affected if Endpoints accept object IDs without verifying the authenticated user owns or has permission to access that specific object
  4. Check for user-to-resource authorization validation
    Search codebase for authorization decorators or permission checks (e.g., 'current_user.id' comparison with resource owner) on sensitive endpoints handling flows, runs, or other user data
    Affected if No ownership verification exists before returning or modifying resources referenced by ID
  5. Test for IDOR via API manipulation
    Using an authenticated session, make an API call to access an object ID belonging to a different user (e.g., GET /api/v1/flows/{other_users_flow_id})
    Affected if The API returns or allows modification of resources belonging to another user without authorization errors

A user is affected if they run Langflow versions 1.0.0 through 1.9.1 and their API endpoints do not validate that the authenticated user owns or has permission to access the requested resource before returning data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.2 or later
Fixed in 1.9.2
Interim mitigation

Implement proper authorization checks on all endpoints that handle sensitive objects, ensuring users can only access resources they are explicitly authorized for. Consider implementing indirect object references and role-based access control (RBAC).

Recommended fix High confidence

1.9.2 or later

  1. 1. Backup your current Langflow installation and all associated data
  2. 2. Check your current Langflow version using: pip show langflow or langflow --version
  3. 3. Review the Langflow 1.9.2 release notes for any important changes or migration instructions
  4. 4. Upgrade Langflow using pip: pip install --upgrade langflow>=1.9.2
  5. 5. Verify the upgrade was successful by checking the new version: pip show langflow
  6. 6. Test that the application starts correctly and IDOR protections are in place
  7. 7. Verify your authentication and authorization controls are working properly
Caveat Review Langflow 1.9.2 release notes for any breaking changes specific to your configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Langflow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7787 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data