CVE-2026-129703
waiting for further signalsZero needs more public information before it can validate it.GHSA-p848-gw9g-wq38 ↗EUVD-2026-126186 ↗
description
vulnerability-lookup installations using the affected feed-key or API-key authentication can create a full web session from a token-authenticated request. An attacker who obtains a feed key or API key can access the associated account and, for administrator accounts, administrative functionality without a password or second factor.
mitigation
Apply the upstream change that keeps feed-key and API-key authentication limited to the current request rather than creating a session; no fixed package version is recorded. Until patched, disable or restrict token-based feed and API access where possible, and invalidate active sessions for accounts whose tokens may have been exposed.
outcome
Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-16 08:36Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-129703
{ "etk_id": "ETK-2026-4573", "cve_id": "CVE-2026-129703", "display_id": "CVE-2026-129703", "ghsa_id": "GHSA-p848-gw9g-wq38", "euvd_id": "EUVD-2026-126186", "status": "published", "anchor_state": "anchored", "title": "Improper session creation in vulnerability-lookup token authentication", "summary": "vulnerability-lookup installations using the affected feed-key or API-key authentication can create a full web session from a token-authenticated request. An attacker who obtains a feed key or API key can access the associated account and, for administrator accounts, administrative functionality without a password or second factor.", "mitigation": "Apply the upstream change that keeps feed-key and API-key authentication limited to the current request rather than creating a session; no fixed package version is recorded. Until patched, disable or restrict token-based feed and API access where possible, and invalidate active sessions for accounts whose tokens may have been exposed.", "vendor": "vulnerability-lookup", "product": "vulnerability-lookup", "affected": [ { "affected_notes": [], "affected_ranges": [ "unspecified" ], "ecosystem": null, "fixed_versions": [], "package_name": "vulnerability-lookup", "purl": null } ], "cwes": [ 287 ], "cvss_score": 7.8, "cvss_src": "cna_vendor", "cvss_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", "epss_score": 0.0031, "epss_percentile": 0.2447, "epss_asof": "2026-11-17", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 29.734936483333332, "t0_at": "2026-11-16T08:36:51.005000+00:00", "signals": { "trigger_signal": { "at": "2026-11-16T08:36:51.005000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-16T08:36:51.005000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-129703" } } }
published 2026-11-16 08:58Z
last change 2026-11-18 20:02Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.