CVE-2026-129703

7.8High

Published 16 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.8CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
Limited impact
Weakness
CWE-287, CWE-613

What an attacker gets

Attackers can gain full administrative access to any user account by using a leaked feed URL or API key. No password or interaction is required, and sessions persist even after the original key is revoked.

Root cause

The application incorrectly calls Flask-Login's login_user() function within authentication decorators, which creates a persistent session cookie instead of just authenticating the single request.

Affected versions

Versions not listed — check the vulnerability-lookup project repository.

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Fix & remediation

Update to the latest version from the project repository. As an interim mitigation, rotate all existing API keys and feed URLs, and manually clear active session cookies in the database.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

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

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-129703