CVE-2026-13448
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.1 Lanflow OSS contains an unauthenticated remote code execution vulnerability in the public flow build endpoint ( /api/v1/build_public_tmp/{flow_id}/flow ). The vulnerability stems from an incomplete denylist in the validate_public_flow_no_code_execution() function that fails to block several code-execution agent components including OpenDsStarAgent, CodeActAgentSmolagents, and CSVAgent.
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-1.10.1 contains an unauthenticated remote code execution vulnerability in the public flow build endpoint (/api/v1/build_public_tmp/{flow_id}/flow). The validate_public_flow_no_code_execution() function uses an incomplete denylist that fails to block dangerous code-execution agents including OpenDsStarAgent, CodeActAgentSmolagents, and CSVAgent, allowing unauthenticated attackers to achieve RCE.
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.10.2CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Langflow installation and versionRun 'pip show langflow' or check your package manager to determine the installed Langflow version. Compare against the affected range: >=1.0.0 and <1.10.2Affected if Version is 1.0.0 through 1.10.1 inclusive
-
Check if the /api/v1/build_public_tmp endpoint is exposedReview your web server or reverse proxy configuration to determine if the /api/v1/build_public_tmp/{flow_id}/flow endpoint is publicly accessible without authenticationAffected if The endpoint is exposed to unauthenticated network access
-
Verify the validate_public_flow_no_code_execution functionInspect the Langflow source code in the validation module that contains validate_public_flow_no_code_execution(). Check if the denylist includes 'OpenDsStarAgent', 'CodeActAgentSmolagents', and 'CSVAgent'Affected if The denylist is missing one or more of these three agents
-
Confirm agent availability in the environmentCheck if the Langflow installation includes the agent packages (OpenDsStarAgent, CodeActAgentSmolagents, CSVAgent) by examining installed Python packages or the agents directory in the Langflow codebaseAffected if Any of these agent types are installed and usable within the Langflow environment
You are affected if Langflow version is 1.0.0-1.10.1, the build_public_tmp endpoint is network-accessible, and the vulnerable agents are present in your environment.
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.10.2
Upgrade to a patched version of IBM Langflow OSS. As an interim measure, restrict network access to the affected public flow build endpoint until patching is complete.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13448 — 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-13448 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