---
id: "CVE-2026-129703"
page: "https://infrastack.ai/live/CVE-2026-129703"
kind: "vulnerability"
aliases: ["CVE-2026-129703"]
title: "vulnerability-lookup: feed and API keys issue full browser login sessions"
severity: "high"
cvss: 7.8
epss: 0.00312
exploited: false
status: "open"
category: "other"
products: [{"name": "vulnerability-lookup", "fixed": [], "affected": "unknown start; no release with the fix found (latest seen v6.4.0)", "ecosystem": "github"}]
ecosystems: ["github"]
tags: ["api-keys", "other", "rss", "self-hosted", "vulnerability-lookup"]
not_affected_if: ["no-api-keys", "no-feed-keys"]
published_at: "2026-11-16T09:17:13+00:00"
first_seen_at: "2026-11-16T10:12:13+00:00"
updated_at: "2026-11-16T18:53:18+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129703", "first_seen_at": "2026-11-16T10:12:13+00:00"}, {"source": "analyst", "url": "https://github.com/vulnerability-lookup/vulnerability-lookup/releases", "first_seen_at": "2026-11-16T10:13:22+00:00", "cites": ["https://github.com/vulnerability-lookup/vulnerability-lookup/releases"]}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-129703", "first_seen_at": "2026-11-16T18:53:18+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00312, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-129703"}]
---

# vulnerability-lookup: feed and API keys issue full browser login sessions

Link for people: https://infrastack.ai/live/CVE-2026-129703 (this .md is for agents)

A feed key or API key sent in a URL parameter or header makes the server set a login session cookie for the account. Anyone holding a leaked feed URL or API key can open a logged-in session, including the admin interface for admin accounts.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- github:vulnerability-lookup affected unknown start; no release with the fix found (latest seen v6.4.0) fixed no fixed version listed

## How to check

- Find your version: check the vulnerability-lookup checkout or release tag; the sources name no affected range, and v6.4.0 (5 Nov 2026) is the latest release seen, so treat it and earlier as unpatched unless your tree contains commit 3605d5b.
- Check the code: grep for login_user in website/decorators.py (auth_feedkey_func) and website/web/api/v1/common.py (auth_func). A call there means you are exposed; the fix sets g._login_user instead.
- Test: request a page with X-API-KEY header or ?X-FEED-KEY=... and see whether the response sets a session cookie.

## Fix

Fixed in the maintainer's commit 3605d5b65d340343cc4b612d40d454afed84302b on the main branch (16 Nov 2026). No release containing it was found; latest release seen is v6.4.0 (5 Nov 2026). Until a release ships, deploy from a checkout that includes the commit. Also: rotate any feed or API key that may have leaked, and note that sessions already created stay valid until they expire (revoking the key does not end them); the maintainers track that separately (CWE-613, CVE-2026-129706).

## Timeline

- 2026-11-16T10:12:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-129703
- 2026-11-16T10:13:22+00:00 analyst https://github.com/vulnerability-lookup/vulnerability-lookup/releases — Read maintainer commit 3605d5b (16 Nov 2026): replaces login_user() with g._login_user in both decorators. No release carries it yet on the releases page (latest v6.4.0, 5 Nov); affected range not stated by any source.
- 2026-11-16T18:53:18+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-129703

## Documents

- [advisory] fix: [security] A feed key or an API key no longer opens a web session https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b
- [fix] fix: [security] A feed key or an API key no longer opens a web session https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b
- [mentions] vulnerability-lookup releases (latest v6.4.0, 5 Nov 2026) https://github.com/vulnerability-lookup/vulnerability-lookup/releases

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
