Disclosed weakness · no CVE recorded

Langflow password changes could leave earlier login sessions usable

Langflow · Langflow · native authentication

First documented disclosure · Review checkpoint

Summary

Changing a password did not invalidate the user’s existing native access and refresh tokens.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reviewed sources describe a correction or controlled reproduction; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Native tokens were not bound to a session version that rotates on persisted password changes.

Conditions required

A previously issued native token remains available after a user password change or administrator reset.

Potential impact

A holder of an earlier session could retain account access after the password change.

Affected versions and configurations

The reviewed upstream report does not establish a complete affected-release range.

Fix and mitigation status

1.13.3 contains the correction. All workers require updated code for consistent revocation.

Practical next steps

Upgrade every worker to 1.13.3 and complete the migration before relying on password-change revocation. API keys require separate handling.

Operating lesson

Credential recovery should revoke the sessions that preceded it.

Evidence and limits

Existing sessions are preserved during upgrade through a nullable session version; API keys deliberately retain their earlier behavior. Tagged verification: access and refresh token checks compare the token session version with the user’s current version.

Sources