NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · Langflow

CVE-2026-55423: Langflow: Logout button does not clear session

mediumCVSS 3.1 6.1GHSA-7hw8-6q6r-4276

In Langflow before 1.7.0, the Logout button does not end the browser session. The auth cookies stay in place, so the next person at the same browser is still signed in as the previous user. Upgrade to Langflow 1.7.0. The risk is mainly on shared computers.

Published Jun 19, 2026 · Updated Sep 24, 2026 · Analysis Oct 25, 2026

What an attacker can do

The /logout endpoint in src/backend/base/langflow/api/v1/login.py deleted the auth cookies without the httponly, samesite, secure and domain values they were set with. Browsers only delete a cookie when those attributes match, so the cookies survived. The frontend also did not clear them. The PR names three cookies: refresh_token_lf, access_token_lf and apikey_tkn_lflw. The reporter saw access_token_lf stay in both Local Storage and Cookies, and refresh_token_lf stay in Cookies. Pressing refresh after Logout returned to the previous screen.

The reporter tested with auto-login off (LANGFLOW_AUTO_LOGIN false) and a set superuser, secret key and password, so authentication was on. The attacker needs physical access to the same browser profile, which matches the vector (AV:P). They then get everything the previous user could do in Langflow: flows, stored credentials and API keys the user can see, and the ability to run flows. Users of shared or kiosk machines who believe they signed out are the ones at risk. Remote attackers gain nothing from this alone.

Who is affected

Langflow versions before 1.7.0 with authentication on. Auto-login mode was not the tested setup. Check the installed version:

pip show langflow

If you run the Docker image, check the image tag.

langflow

Ecosystem
PyPI
Affected
< 1.7.0
Fixed in
1.7.0
Check
pip show langflow

How to fix it

Upgrade to Langflow 1.7.0 or later.

pip install --upgrade "langflow>=1.7.0"

Pull requests 10527 and 10528 make the logout endpoint delete the cookies with the same parameters used to create them, and make the frontend clear the auth cookies on logout. The advisory gives no workaround. Until you upgrade, users on shared machines should clear cookies and Local Storage for the Langflow site by hand, or close the browser profile after signing out.

How to tell if you were hit

On a shared machine, open the browser developer tools after clicking Logout and check Application > Cookies and Local Storage for access_token_lf, refresh_token_lf and apikey_tkn_lflw. If they are still present, the session is not ended. On the server, look for requests from the same user session after a logout time, or from a different person using the same browser. There is no distinct server log line for this flaw.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Summary

The logout button does not clear the session. The previous user stays logged in unless another user explicitly logs in.

Details

Not in auto login mode. Hosted on localhost. access_token_lf remains present in both Local Storage and Cookies. refresh_token_lf remains present in Cookies.

Root cause: the /logout endpoint deleted the authentication cookies without matching the original httponly/samesite/secure/domain parameters, so the browser kept them; additionally the frontend did not clear the auth cookies on logout.

LANGFLOW_AUTO_LOGIN: "False"
LANGFLOW_SUPERUSER: <set>
LANGFLOW_SUPERUSER_PASSWORD: <set>
LANGFLOW_SECRET_KEY: <set>
LANGFLOW_NEW_USER_IS_ACTIVE: "False"
LANGFLOW_ENABLE_SUPERUSER_CLI: "False"

PoC

Click Logout. Hit refresh to return to previous screen.

Impact

Users on shared computers may falsely believe they have terminated their session.

Patches

Fixed in 1.7.0 (PRs #10527 and #10528). The logout endpoint now deletes the auth cookies using the same parameters they were created with, and the frontend clears the auth cookies on logout. Upgrade to 1.7.0 or later.

Credited to iann0036, Cristhianzl, AntonioABLima, andifilhohub, massif-01, cookesan.

Questions

Can someone exploit this remotely?

Not on its own. The attacker needs access to the same browser profile after the victim clicks Logout, hence the physical-access vector. It does not expose sessions over the network.

Which Langflow version fixes the logout bug?

Langflow 1.7.0. Everything before it is affected. The fix is in pull requests 10527 and 10528.

Is clearing the cookies by hand enough on an old version?

It removes the leftover session for that browser. The advisory gives no official workaround, though. Clear both cookies and Local Storage, because the access token was kept in both.

Is CVE-2026-55423 exploited in the wild?

No source says so, and it is not in CISA's KEV catalog.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Langflow vulnerabilities

All Langflow entries