AI Science Tracker

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

vulnerability-lookup · AI involvement attributed to Claude Opus 5.5

Finding and attribution

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

Product: vulnerability-lookup. AI system: Claude Opus 5.5. Team / organization: CIRCL (CNA); AI attribution as credited in the CVE record.

CVE identifiers: CVE-2026-129703.

AI and human contribution (source account): The CNA record credits 'Michael Reimsbach; Cédric Bonhomme; Claude Opus 5.5; Claude Opus 5.5'. It states the AI attribution as written there and does not describe the model's operation, autonomy or the human validation steps; none is inferred.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The CNA record establishes a coordinated disclosure with the credit above. It does not establish exploitation in the wild or a zero-day incident.

Remediation status: fix documented. CNA record 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 Deployed patch status is not checked.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 16 Nov 2026. AI attribution dated 16 Nov 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 7.8. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-129703: CVSS 4.0 · 7.8 (High) · 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. CIRCL (CNA; CVE Program record) · checked 17 Nov 2026.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: CNA record 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 Deployed patch status is not checked.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases