CVE-2026-8182
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.10.3 installations allow anyone on the internet to execute arbitrary code on the server without any credentials via 2 HTTP requests.
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 · moderate confidenceIBM Langflow OSS versions 1.0.0 through 1.10.3 contain a critical authentication bypass vulnerability that allows unauthenticated remote attackers to execute arbitrary code on the server through only two HTTP requests. The vulnerability appears to stem from a flaw in the authentication mechanism that can be bypassed without any credentials.
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.11.0CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Identify installed Langflow versionRun 'pip show langflow' or check the docker image tag. If running as a service, check the version endpoint (e.g., /api/v1/version or /health)Affected if Version is 1.0.0 through 1.10.3 (less than 1.11.0)
-
Confirm Langflow service is runningCheck if the Langflow process is active: 'ps aux | grep langflow' or 'docker ps | grep langflow'. Note the listening port (default 7860)Affected if Service is running and accessible on a network interface
-
Verify network exposureCheck binding address in config or run 'netstat -tlnp | grep <port>' to see if listening on 0.0.0.0 vs 127.0.0.1. Review firewall rules or reverse proxy settingsAffected if Service binds to 0.0.0.0 or is reachable from non-local networks without proper access controls
-
Test authentication enforcementSend an unauthenticated HTTP request to API endpoints (e.g., GET /api/v1/flows) and observe if the server returns 401/403 or allows accessAffected if Unauthenticated requests return successful responses (200) instead of authentication errors
You are affected if Langflow version is below 1.11.0 AND the service is network-accessible, allowing unauthenticated attackers to reach API endpoints.
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 data1.11.0
Immediately upgrade to the latest version of IBM Langflow OSS past 1.10.3. If immediate patching is not possible, restrict network access to the Langflow service using network segmentation or firewall rules to prevent unauthorized internet access.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8182 — 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-8182 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