Description
Express Gateway through 1.16.11 contains an authentication bypass vulnerability in the OAuth 2.0 refresh_token grant that fails to validate the token secret or issuing client. Attackers with any valid client credentials and the identifier portion of another user's refresh token can obtain that user's access token and impersonate them against oauth2-protected APIs.
Published: 2026-10-07
Score: 7.6 High
EPSS: n/a
KEV: No
Impact: Unauthorized Access / Impersonation
Action: Immediate Patch
AI Analysis

Impact

Express Gateway through version 1.16.11 is vulnerable to an authentication bypass in the OAuth 2.0 refresh_token grant; validation fails to confirm the token secret or the issuing client, allowing an attacker with valid client credentials and the identifier of another user's refresh token to obtain that user's access token and impersonate them against any API protected by OAuth 2.0.

Affected Systems

The vulnerability affects the Express Gateway product, a Node.js based API gateway framework. All releases through and including 1.16.11, including the official Docker image, are impacted. No other vendors or product versions are listed in the CNA data for this flaw.

Risk and Exploitability

The flaw scores a CVSS 7.6, indicating high severity. Its EPSS score is unavailable and it is not listed in CISA's KEV catalog. The attack vector is likely remote, using the standard OAuth 2.0 token exchange endpoint; an attacker only needs legitimate client credentials and the target refresh token identifier, no further privileged access. Because validation is bypassed, the attacker can stealthily obtain any user's access token, enabling impersonation of that user on protected APIs.

Generated by OpenCVE AI on October 7, 2026 at 15:29 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Express Gateway to any version newer than 1.16.11 so the refresh token validation fix is applied.
  • If an upgrade is not immediately possible, disable or restrict the OAuth 2.0 refresh_token grant for untrusted clients and enforce strict client-credential checks before issuing new tokens.
  • Implement monitoring and logging of refresh token exchanges to detect anomalous patterns where a client obtains tokens associated with other users.

Generated by OpenCVE AI on October 7, 2026 at 15:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 07 Oct 2026 13:00:00 +0000

Type Values Removed Values Added
Description Express Gateway through 1.16.11 contains an authentication bypass vulnerability in the OAuth 2.0 refresh_token grant that fails to validate the token secret or issuing client. Attackers with any valid client credentials and the identifier portion of another user's refresh token can obtain that user's access token and impersonate them against oauth2-protected APIs.
Title Express Gateway through 1.16.11 OAuth 2.0 Refresh Token Validation Bypass
First Time appeared Express-gateway
Express-gateway express-gateway Docker Image
Weaknesses CWE-287
CPEs cpe:2.3:a:express-gateway:express-gateway_docker_image:*:*:*:*:*:*:*:*
Vendors & Products Express-gateway
Express-gateway express-gateway Docker Image
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 7.6, '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'}


Subscriptions

Express-gateway Express-gateway Docker Image
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-07T12:48:18.499Z

Reserved: 2026-10-07T11:02:13.828Z

Link: CVE-2026-107162

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-07T13:17:19.963

Modified: 2026-10-07T16:02:27.613

Link: CVE-2026-107162

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-07T15:30:17Z

Weaknesses