CVE-2026-10560
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.6 contains a missing authentication vulnerability in /api/v1/build_public_tmp/ endpoints that allows an unauthenticated attacker to read build event data or cancel jobs using a valid job identifier, resulting in information disclosure and denial of service.
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.6 has a missing authentication vulnerability in the /api/v1/build_public_tmp/ API endpoint. This allows unauthenticated attackers to read build event data or cancel running jobs by providing a valid job identifier, leading to information disclosure and denial of service.
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.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Langflow versionRun 'pip show langflow' or check the installed package version via your package manager. If running from source, check the version file or git tag.Affected if The installed version is >= 1.0.0 and <= 1.9.6
-
Verify API endpoint is exposedLocate your Langflow server configuration and determine if the /api/v1/build_public_tmp/ endpoint is accessible on the network (check your web server config, reverse proxy settings, or firewall rules).Affected if The endpoint is reachable from the network where untrusted users could access it
-
Test endpoint authentication requirementSend an unauthenticated HTTP request to the /api/v1/build_public_tmp/ endpoint (for example: curl -X GET http://your-server:7860/api/v1/build_public_tmp/test-job-id). Observe whether the server returns a 401/403 or accepts the request without requiring auth credentials.Affected if The server accepts the request without returning an authentication error (401 Unauthorized or 403 Forbidden)
-
Check job cancellation capabilityIf you have a valid job identifier from a previous build, send an unauthenticated DELETE request to /api/v1/build_public_tmp/{job_id} and observe if the server processes it without requiring authentication.Affected if The DELETE request succeeds without authentication
You are affected if you are running Langflow version 1.0.0 through 1.9.6 and the /api/v1/build_public_tmp/ endpoint is accessible without authentication credentials.
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 dataAdd authentication and authorization checks to the /api/v1/build_public_tmp/ endpoint to ensure only authenticated and authorized users can access build event data and control job execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10560 — 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-10560 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