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


- **Severity:** High 7.6 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 10 Oct 2026
- **Also known as:** GHSA-p6v9-9m69-qjxm

## What is CVE-2026-107162?

CVE-2026-107162 is a high-severity vulnerability in ExpressGateway express-gateway, published on 7 Oct 2026. 

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-107162?


## How do I fix CVE-2026-107162?

No fix has been published for CVE-2026-107162 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107162 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107162 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107162 and fix it if it is affected.

What it is: CVE-2026-107162 is a high-severity vulnerability in ExpressGateway express-gateway, published on 7 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107162 exists.

Affected product: ExpressGateway express-gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107162/ (Markdown: https://insights.sbomify.com/CVE-2026-107162/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107162
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107162
- OSV: https://osv.dev/vulnerability/CVE-2026-107162

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107162/
Summaries are generated and may contain mistakes; the official description above is the record.