CVE-2026-10134
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 · uneditedIBM Langflow OSS 1.0.0 through 1.9.3 allows an attacker to read every secret available to the Langflow process, read and modify every flow, conversation, message, file upload, and saved component in the Langflow database, can connect to internal services, abuse cloud metadata endpoints, laterally move to other tenants on the same Langflow instance, and Establish persistence by modifying the public flow's `tool_code` so normal `/api/v1/build/...` calls by any user re-execute attacker code at each build.
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 confidenceIBM Langflow OSS versions 1.0.0 through 1.9.3 contains a critical authentication/authorization flaw (likely unauthenticated API access or severe IDOR) allowing attackers to read all secrets, read/write all database records (flows, conversations, messages, files, components), pivot to internal services/cloud metadata, and achieve persistent code execution via modified tool_code in public flows that triggers on legitimate /api/v1/build/... calls.
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>= 1.0.0, <= 1.9.3CVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify installed Langflow versionRun 'pip show langflow' or check the package version in your Python environment to identify the exact version numberAffected if The installed version is 1.0.0 through 1.9.3 inclusive
-
Confirm Langflow API is network accessibleCheck if the Langflow server API endpoints (such as /api/v1/...) are exposed to network access without proper authentication controlsAffected if The API is accessible without authentication from untrusted networks
-
Inspect stored flows for unauthorized tool_codeReview flow configurations in the Langflow database or file storage for any unexpected or malicious tool_code entries, particularly in public flowsAffected if Flows contain tool_code that was not authored by your organization or contains suspicious code execution patterns
-
Audit access logs for unauthorized API callsReview Langflow access logs for API calls to /api/v1/build/... endpoints originating from unexpected sources or showing anomalous data access patternsAffected if Logs show unauthorized access to secrets, database records, or internal service endpoints
-
Check for signs of data exfiltrationExamine whether secrets, flow data, or internal metadata have been accessed or exported from the Langflow instance by unauthorized partiesAffected if Evidence exists of unauthorized reads or exports of sensitive data, secrets, or internal service metadata
You are affected if your Langflow installation is version 1.0.0 through 1.9.3 and the API is accessible without proper authentication, or if you find evidence of unauthorized data access or malicious tool_code in your flows.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImmediately upgrade to a patched version; if unavailable, restrict network access to the Langflow instance, rotate all secrets, audit for compromise, and rebuild or sanitize all flows to remove any injected tool_code.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10134 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10134 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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