CVE-2026-17632
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 could allow a remote authenticated attacker to execute arbitrary code due to improper validation of Python code during AST-based security scanning.
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 versions 1.0.0 through 1.10.3 contains a vulnerability where the AST-based security scanning mechanism that validates Python code is improperly implemented, allowing an authenticated remote attacker to bypass the validation and execute arbitrary Python code on the system.
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 package version in your Python environmentAffected if Version is 1.0.0 through 1.10.3 (any version >=1.0.0 and <1.11.0)
-
Confirm Langflow service is runningCheck if the Langflow application is active and accessible on its configured port (typically 7860 or 3000)Affected if Langflow service is running with a vulnerable version
-
Verify AST security scanner is enabledInspect Langflow configuration files or environment variables for AST_SECURITY_SCAN, CODE_VALIDATION, or similar security scanning settingsAffected if AST-based code validation is enabled (this is the default behavior for code execution features)
-
Check for exposed API endpointsReview network-accessible endpoints that accept Python code input, such as custom component creation or flow execution APIsAffected if API endpoints that process user-supplied Python code are accessible
-
Review authentication statusVerify whether the Langflow instance requires authentication for code execution featuresAffected if The vulnerability requires an authenticated session, so check if user authentication is enforced on your instance
Your environment is affected if Langflow version is 1.0.0 through 1.10.3 and the AST-based security scanner is processing Python code from authenticated users.
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.
dbcve · scoped1.11.0
Upgrade IBM Langflow to a version beyond 1.10.3 that properly validates Python code within the AST-based security scanner to prevent code injection.
IBM Langflow 1.10.4 or later
- 1. Backup your current IBM Langflow installation and all associated data
- 2. Stop the IBM Langflow service
- 3. Upgrade to IBM Langflow version 1.10.4 or later using your package manager (e.g., pip install langflow==1.10.4)
- 4. Verify the upgrade was successful by checking the installed version (pip show langflow)
- 5. Restart the IBM Langflow service
- 6. Test that the application functions normally and the AST-based security scanning now properly validates Python code
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-17632 — 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-17632 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