CVE-2026-129703

vulnerability-lookup: Feed key or API key authentication creates full web session bypassing password and 2FA

Published Nov 16, 2026 CVSS 4.0 · 7.8 High EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability allows an attacker who possesses a leaked feed URL or API key to create a full authenticated web session without a password or 2‑factor authentication, exploiting a CWE‑287 Authentication Bypass flaw and a CWE‑613 Insufficient Session Clearance weakness. By exploiting the login_user call embedded in the authentication decorators, the request sets a session cookie that grants complete access to all pages, including admin interfaces for privileged accounts. The resulting session survives until expiration and cannot be invalidated by revoking the compromised key.

Affected Systems

The affected product is the vulnerability‑lookup web application. All users whose feed key or API key is exposed are vulnerable; there is no product version detail available, so assume the current release is impacted until noted otherwise.

Risk and Exploitability

The CVSS score of 7.8 indicates a high severity. EPSS is not available, but the ease of exploitation is clear: no prior authentication, special network conditions or user interaction are required, just a single HTTP request with the token. Because the vulnerability is listed as not part of the CISA KEV catalog, there is no known, publicly‑available exploit, yet the impact warrants proactive remediation.

Remediation

Vendor Solution

The authentication decorators for feed-key and API-key requests no longer call Flask-Login's login_user(), which was writing the authenticated user into the session cookie and creating a full web session. Instead, the user object is now stored on Flask's request-scoped g._login_user attribute, which Flask-Login's current_user property reads first. This authenticates only the current request without setting any session cookie, preventing a limited-scope token from being elevated to a persistent, all-pages session that bypasses password and two-factor authentication.


OpenCVE Recommended Actions

  • Deploy the fix that removes the use of login_user in the authentication decorators – for example, upgrade to the latest vulnerability‑lookup version containing commit 3605d5b65d340343cc4b612d40d454afed84302b.
  • Immediately revoke and rotate any feed or API keys that have been exposed or are believed to be compromised, and generate new keys for affected users.
  • Enable or enforce additional multi‑factor authentication for administrator accounts and monitor authentication logs for suspicious or prolonged session activity.

Generated by OpenCVE AI on November 16, 2026 at 09:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Circl
Circl vulnerability-lookup
Vendors & Products Circl
Circl vulnerability-lookup
Type Values Removed Values Added
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.
Title vulnerability-lookup: Feed key or API key authentication creates full web session bypassing password and 2FA
First Time appeared Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup
Weaknesses CWE-287
CWE-613
CPEs cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*
Vendors & Products Vulnerability-lookup
Vulnerability-lookup vulnerability-lookup
References
Metrics cvssV4_0

{'score': 7.8, 'vector': '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'}

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
CIRCL
Published
Updated
Nov 16, 2026, 8:36 AM
Reserved
Nov 16, 2026, 8:36 AM
Status
Received
Published
Nov 16, 2026, 9:17 AM
Modified
Nov 16, 2026, 9:17 AM