CVE-2026-129703: high-severity vulnerability in vulnerability-lookup
vulnerability-lookup: Feed key or API key authentication creates full web session bypassing password and 2FA
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.8epss 0.3%
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.
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
Affected products
vulnerability-lookup · vulnerability-lookupRelated CVEs — vulnerability-lookup
In the same product, most dangerous first.
CVE-2026-73374MEDIUMStored Cross-Site Scripting (XSS) via Unescaped CNA Reference Tags in vulnerability-lookupEPSS 0.6%CVE-2026-73405MEDIUMAuthorization Bypass in SSE Pub/Sub Allows Unconfirmed Accounts to Access Stream Events in vulnerability-lookupEPSS 0.5%CVE-2026-72761MEDIUMWebhook SSRF guard bypassed by IPv6 transition addresses (NAT64/6to4/Teredo pass is_global check) in vulnerability-lookupEPSS 0.5%CVE-2026-73432MEDIUMStored Server-Side Request Forgery in Remote-Instance Synchronization Allows Access to Internal Services in vulnerability-lookupEPSS 0.4%CVE-2026-73431HIGHReusable Account Activation and Recovery Tokens Allow Repeated Account Takeover in vulnerability-lookupEPSS 0.4%CVE-2026-133611MEDIUMvulnerability-lookup: 2FA Disabled via Unauthenticated GET Request and Unpublished Comments Accessible Without AuthorizationEPSS 0.3%