The affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application.
The security impact is that a user cannot effectively revoke an attacker's access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user's profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely.
Metrics
Affected Vendors & Products
No advisories yet.
Solution
The session identifier is now bound to the user's current password hash. User.get_id() returns a composite string of the form '<user_id>:<digest>', where the digest is an HMAC-SHA256 of the stored password hash keyed with the application SECRET_KEY. The load_user callback validates that the digest in the session matches the digest computed from the user's current password hash using a constant-time comparison (hmac.compare_digest). If the password has changed, the digest no longer matches and the session is rejected, effectively logging out all sessions that were opened under the previous credential. When a user changes their own password through the profile page, they are immediately re-authenticated via login_user() so their current session is renewed with the new digest while all other sessions are invalidated.
Workaround
No workaround given by the vendor.
Mon, 16 Nov 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned self.id). Because the session ID contained no component derived from the user's credential, it remained valid indefinitely regardless of any subsequent password change, account recovery, or administrator-initiated password reset. An attacker who had obtained a valid session for a user account (for example through cross-site scripting, session hijacking, or a previously exposed feed or API key) could continue to access that user's account after the user changed their password, because the session cookie still carried the same static user ID and the user_loader accepted it without any credential-bound validation. The affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application. The security impact is that a user cannot effectively revoke an attacker's access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user's profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely. | |
| Title | vulnerability-lookup: Session Persists After Password Change (CWE-613) | |
| First Time appeared |
Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup |
|
| Weaknesses | CWE-613 | |
| CPEs | cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup |
|
| References |
| |
| Metrics |
cvssV4_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CIRCL
Published:
Updated: 2026-11-16T08:46:47.377Z
Reserved: 2026-11-16T08:46:40.876Z
Link: CVE-2026-129706
No data.
Status : Received
Published: 2026-11-16T09:17:13.487
Modified: 2026-11-16T09:17:13.487
Link: CVE-2026-129706
No data.
OpenCVE Enrichment
No data.