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

> Anyone with a leaked feed key or API key can get a full web session in vulnerability-lookup, including admin access.

- **Severity:** High 7.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-p848-gw9g-wq38

## What is CVE-2026-129703?

CVE-2026-129703 is a high-severity authentication bypass vulnerability in vulnerability-lookup, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-129703?

It affects 1 product.

An affected version is exposed as installed. No special setting or call is needed.


Products: Vulnerability-Lookup.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*` from unspecified up to unspecified

## How do I fix CVE-2026-129703?

No fix has been published for CVE-2026-129703 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129703 being exploited?

There is no known exploitation of CVE-2026-129703 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129703 and fix it if it is affected.

What it is: CVE-2026-129703 is a high-severity authentication bypass vulnerability in vulnerability-lookup, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129703 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: vulnerability-lookup. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129703/ (Markdown: https://insights.sbomify.com/CVE-2026-129703/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129703
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129703
- OSV: https://osv.dev/vulnerability/CVE-2026-129703

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129703/
Summaries are generated and may contain mistakes; the official description above is the record.
