CVE-2026-107162: Express Gateway through 1.16.11 OAuth 2.0 Refresh Token Validation Bypass

Published Oct 7, 2026
·
Updated

Express Gateway through 1.16.11 contains an authentication bypass vulnerability in the OAuth 2.0 refreshtoken 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.

Affected Software

1 affected component
Express Gateway Express Gateway<=1.16.11

Event History

Oct 7, 2026
CVE Published
via MITRE·12:48 PM
Data Sourced
via MITRE·12:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Express Gateway releases through 1.16.11 are affected where the OAuth 2.0 refresh_token grant is used.

2

Does an attacker need the victim's client credentials or full refresh token?

No. The attacker needs any valid client credentials plus the identifier portion of another user's refresh token; the vulnerable flow does not validate the token secret or issuing client.

3

What can an attacker do after exploiting the issue?

They can obtain the targeted user's access token and impersonate that user against OAuth 2.0-protected APIs.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203