CVE-2026-107162
validatedZero produced an exploit or a check.GHSA-p6v9-9m69-qjxm ↗EUVD-2026-94316 ↗
description
Express Gateway through 1.16.11 is affected in its OAuth 2.0 refresh-token grant processing. An attacker with valid client credentials and another user’s refresh-token identifier may obtain an access token for that user and act as them against protected APIs.
mitigation
Disable the OAuth 2.0 refresh-token grant where feasible, and restrict access to affected token endpoints to trusted clients and networks. Monitor for unexpected token issuance and rotate potentially exposed refresh tokens.
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-07 12:48Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-107162
{ "etk_id": "ETK-2026-873", "cve_id": "CVE-2026-107162", "display_id": "CVE-2026-107162", "ghsa_id": "GHSA-p6v9-9m69-qjxm", "euvd_id": "EUVD-2026-94316", "status": "published", "anchor_state": "anchored", "title": "OAuth refresh-token authentication bypass in Express Gateway", "summary": "Express Gateway through 1.16.11 is affected in its OAuth 2.0 refresh-token grant processing. An attacker with valid client credentials and another user’s refresh-token identifier may obtain an access token for that user and act as them against protected APIs.", "mitigation": "Disable the OAuth 2.0 refresh-token grant where feasible, and restrict access to affected token endpoints to trusted clients and networks. Monitor for unexpected token issuance and rotate potentially exposed refresh tokens.", "vendor": "ExpressGateway", "product": "express-gateway", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0, <= 1.16.11" ], "ecosystem": null, "fixed_versions": [], "package_name": "express-gateway", "purl": null } ], "cwes": [ 287 ], "cvss_score": 7.6, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N", "epss_score": 0.0029, "epss_percentile": 0.2004, "epss_asof": "2026-10-21", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 20.809527483333333, "t0_at": "2026-10-07T12:48:18.499000+00:00", "signals": { "check": { "at": "2026-10-07T14:12:47.709567+00:00", "days": 0.058671418599537034, "is_lower_bound": false, "measured_at": "2026-10-07T12:48:18.499000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-07T12:48:18.499000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-07T12:48:18.499000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-107162" } } }
published 2026-10-07 13:51Z
last change 2026-10-21 21:36Z
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.