Langflow addressed CVE-2026-93680 by disabling auto-login by default in 1.13.0. That default matters for new installations, but an existing deployment can still explicitly set LANGFLOW_AUTO_LOGIN=true. An upgrade does not automatically remove that operator-level choice or invalidate all previously issued sessions and API keys. Treating any 1.13.0 install as…
Inspect the ClaimsCase · DiggingBeagle record
Langflow 1.13.0 changed auto-login defaults without overriding explicit insecure settings
An authentication configuration default changed in Langflow 1.13.0, but operators retaining an explicit auto-login setting may remain exposed.
Scope
Langflow configuration-sensitive authentication behavior, with explicit auto-login overrides potentially preserving insecure access after updating to 1.13.0.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- fixed reported
- AI role
- AGAINST AI
Basis and provenance
IBM and Langflow document the new default and remaining explicit override; the analysis does not claim every installation was accessed. Impact remains unrated because the scoped record does not establish a calibrated severity-to-impact-band mapping.
Assessed Oct 31, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-C26-LANGFLOW-AUTOLOGIN-DEFAULT-1 · IBM Langflow OSS multi-vulnerability bulletin for 1.13.0
At a glance
Package version and effective deployment authorization are different facts; an upgraded old configuration may still allow auto-login.
Read the implicationsWhether specific previously issued sessions need revocation depends on deployment configuration. The public bulletin does not establish compromise of arbitrary Langflow tenants.
Limits and uncertaintyFull account
Langflow addressed CVE-2026-93680 by disabling auto-login by default in 1.13.0. That default matters for new installations, but an existing deployment can still explicitly set LANGFLOW_AUTO_LOGIN=true. An upgrade does not automatically remove that operator-level choice or invalidate all previously issued sessions and API keys. Treating any 1.13.0 install as secure without examining its effective environment would therefore mistake a default-setting change for a complete runtime authentication guarantee.
The practical question is what the deployed process actually requires for each API and MCP route. Operators should compare effective environment settings, existing API keys and bootstrap credentials after upgrading. This issue is related to other Langflow security disclosures in the same release but is not an instance of the tool-listing RCE or the generated-component sandbox flaw.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
Timeline
- Oct 29, 2026disclosure
Public disclosure
Claims & evidence
CLM-C26-LANGFLOW-AUTOLOGIN-DEFAULT-1IBM reports that Langflow 1.13.0 disabled auto-login by default to address CVE-2026-93680, while an explicit auto-login environment override can remain active.supported
Basis: reported finding
- supportsIBM Langflow OSS multi-vulnerability bulletin for 1.13.0vendor statement
IBM bulletin, CVE-2026-93680 default-authentication behavior and 1.13.0 correction
Implications
Package version and effective deployment authorization are different facts; an upgraded old configuration may still allow auto-login.
Controls and mitigations
- Check the deployed environment, bootstrap credentials and active sessions/API keys; enforce auth in front of the tool routes after upgrade.
Unknowns and contradictions
- Whether specific previously issued sessions need revocation depends on deployment configuration.
- The public bulletin does not establish compromise of arbitrary Langflow tenants.
Sources and citation
Material revision history
- Oct 31, 2026 · Canonical change recorded · new in release · revision 208