Langflow: Logout button does not clear session

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2026-55423: 0.22% estimated exploitation activity in the next 30 days; percentile 12.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. accesstokenlf remains present in both Local Storage and Cookies. refreshtokenlf 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. 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.

Published by the source

19 Jun 2026, 21:17 UTC

Last modified by the source

24 Sep 2026, 15:00 UTC

Source last checked

26 Oct 2026, 13:54 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7hw8-6q6r-4276

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7hw8-6q6r-4276

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55423

Advisory: Langflow: Logout button does not clear session
IDs: CVE-2026-55423, GHSA-7hw8-6q6r-4276
Record: https://patchnext.com/advisories/cve-2026-55423 (revision 2, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: langflow 1.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI langflow: affected < 1.7.0; fixed in 1.7.0

## Suggested inspection (read-only)
- `python -m pip show langflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on langflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7hw8-6q6r-4276 (OSV record GHSA-7hw8-6q6r-4276 lists affected ranges: PyPI langflow >=0 <1.7.0 (fixed))
- Verified: https://github.com/advisories/GHSA-7hw8-6q6r-4276 (GitHub-reviewed advisory GHSA-7hw8-6q6r-4276 lists affected ranges: PyPI langflow >=0 <1.7.0)

Commands are suggestions: review each one before running it.