CVE-2026-81826

Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed.

This means that if an attacker already possesses a valid session—for example, from prior access or a stolen session token—the victim changing their password does not terminate that attacker’s access. The session remains usable until it expires naturally. The upstream commit describes this directly as:

“session keeps working until it expires.”

The fix detects password changes and explicitly invokes _invalidate_user_sessions(user.id) after the database update. This is applied in both edit_user_core() and admin_edit_user_core().

Version impacted >=3.3.0

Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed.

This means that if an attacker already possesses a valid session—for example, from prior access or a stolen session token—the victim changing their password does not terminate that attacker’s access. The session remains usable until it expires naturally. The upstream commit describes this directly as:

“session keeps working until it expires.”

The fix detects password changes and explicitly invokes _invalidate_user_sessions(user.id) after the database update. This is applied in both edit_user_core() and admin_edit_user_core().

Version impacted >=3.3.0

Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed.

This means that if an attacker already possesses a valid session—for example, from prior access or a stolen session token—the victim changing their password does not terminate that attacker’s access. The session remains usable until it expires naturally. The upstream commit describes this directly as:

“session keeps working until it expires.”

The fix detects password changes and explicitly invokes _invalidate_user_sessions(user.id) after the database update. This is applied in both edit_user_core() and admin_edit_user_core().

Version impacted >=3.3.0

Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed.

This means that if an attacker already possesses a valid session—for example, from prior access or a stolen session token—the victim changing their password does not terminate that attacker’s access. The session remains usable until it expires naturally. The upstream commit describes this directly as:

“session keeps working until it expires.”

The fix detects password changes and explicitly invokes _invalidate_user_sessions(user.id) after the database update. This is applied in both edit_user_core() and admin_edit_user_core().

Version impacted >=3.3.0

Affected versions of Flowintel do not revoke existing authenticated sessions when a user’s password is changed.

This means that if an attacker already possesses a valid session—for example, from prior access or a stolen session token—the victim changing their password does not terminate that attacker’s access. The session remains usable until it expires naturally. The upstream commit describes this directly as:

“session keeps working until it expires.”

The fix detects password changes and explicitly invokes _invalidate_user_sessions(user.id) after the database update. This is applied in both edit_user_core() and admin_edit_user_core().

Version impacted >=3.3.0