PULSE
FEED
ransomqilin reclama a A.I.M Cash & Carry · IE · Retail & E-Commerceransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcareransomqilin reclama a A.I.M Cash & Carry · IE · Retail & E-Commerceransomsilentransomgroup reclama a Q...ransomcurious worm reclama a interdent.com · DE · Healthcareransomrhysida reclama a Waterman Group · GB · Professional Servicesransomransomhouse reclama a Indiabulls Housing Finance · IN · Financial Servicesransomqilin reclama a Power Equipment · AU · Manufacturingransomqilin reclama a Arrigoni SpA · IT · Manufacturingransomplay reclama a Acudor · US · Manufacturingransompanzer reclama a Bjbsayariahransomdaixin reclama a Trustbridge & EmpathHealth · US · Healthcareransomrhysida reclama a Steffen family retail group · Retail & E-Commerceransomincransom reclama a BHIC Bofors Asia · MY · Government & Defenseransomakira reclama a The Mandrel Group · Otherransomn0n reclama a Verastem Oncology (Verastem, Inc.) · US · Healthcare
← All CVEs
CVE WatchNov 16, 2026

CVE-2026-129706

In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned

CVSS

—

No CVSS

EPSS

—

KEV

—

Exploit Today

0

0-100

Published: Nov 16, 2026 · Last modified: Nov 16, 2026 · CWE-613

EPSS · 30d

Not enough EPSS history yet.

Technical 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.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-129703—
—
——0In the vulnerability-lookup web application, the authentication decorators for feed-key requests (auth_feedkey_func in website/decorators.py) and API-key requests (auth_func in website/web/api/v1/common.py) called Flask-Login's login_user() function. This caused the HTTP response to a request authenticated solely by a feed key (supplied as the X-FEED-KEY URL parameter) or an API key (supplied as the X-API-KEY header) to set a session cookie that grants full authenticated access to every page in the application, without requiring a password or two-factor authentication. The practical impact is that any party possessing a leaked feed URL (a common occurrence, as feed URLs are shared with RSS readers) or an API key could obtain a valid web session for the associated account. This session provides access to the user's account page, which exposes the API key and other profile data, and for accounts with the administrator role, access to the /admin interface, enabling full administrative control of the application. The vulnerability affects all users whose feed key or API key is exposed. No prior authentication, user interaction, or special network conditions are required; a single HTTP request with the token is sufficient to establish the session. The session persists until it expires, and because it is not bound to the original credential (a related CWE-613 issue noted by the developers), revoking the feed key or API key does not invalidate the already-created session. The fix replaces the login_user() call with assignment to g._login_user, which Flask-Login's current_user property reads for the current request only, without writing any session cookie. The affected views remain unchanged and continue to see the authenticated user for the single request.8h
CVE-2026-128359—
—
——0When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive.1d
CVE-2026-927386.8 MED
24.0%
——7Vault's Login MFA feature did not consistently enforce the lifetime of pending two-phase login requests. This may allow a user who previously completed the first authentication factor to complete MFA and obtain a Vault token after the pending request should have expired, including after the user's primary credential has been rotated. This vulnerability (CVE-2026-92738) is fixed in Vault Community Edition 2.2.2 and Vault Enterprise 2.2.2, 1.21.14, and 1.19.26.3d
CVE-2026-1283353.7 LOW
25.7%
——8Contao 4.6.0 before 5.3.54, 5.4.0-RC1 before 5.7.17, and 6.0.0-RC1 before 6.0.6 fails to invalidate existing user sessions when two-factor authentication is enabled or disabled. Because Contao\User::isEqualTo() and serialized session data omit two-factor state, attackers already holding a session keep it after the owner changes 2FA settings.3d
CVE-2026-1283304.2 MED
15.3%
——5Miniflux before 2.3.5 contains an insufficient session expiration vulnerability that allows attackers to retain account access because password changes do not revoke existing web sessions. Attackers holding a leaked password or copied session cookie keep access for up to 30 days, reading integration credentials, creating API keys, or registering passkeys.4d
CVE-2026-1280305.9 MED
36.1%
——11OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an insufficient session expiration vulnerability because Mage_Api_Model_Session::_renewBySessId() never checks api_user.is_active and REST OAuth authorization never checks whether the admin user is active. Attackers holding an existing SOAP/XML-RPC session or OAuth access token retain API access after deactivation or API key rotation, reading and modifying customer, order and catalog data.3d