# CVE-2026-107177: Express Gateway through 1.16.11 Hardcoded Default cipherKey Exposes OAuth Tokens

> Attackers with datastore access can decrypt OAuth tokens using a hardcoded key, enabling unauthorized access to user accounts.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-rq2q-fwh6-p47r

## What is CVE-2026-107177?

CVE-2026-107177 is a high-severity vulnerability in ExpressGateway express-gateway, published on 7 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Express Gateway through 1.16.11 contains a hardcoded cryptographic key vulnerability that allows attackers with datastore access to decrypt stored OAuth 2.0 token secrets via the default crypto.cipherKey 'sensitiveKey'. Attackers who can read Redis can decrypt tokenEncrypted values and combine them with stored token IDs to obtain valid bearer tokens for any user.

Weakness: CWE-1394 (Use of Default Cryptographic Key)

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


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

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

## Is CVE-2026-107177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107177 is a high-severity vulnerability in ExpressGateway express-gateway, published on 7 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107177 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-107177/ (Markdown: https://insights.sbomify.com/CVE-2026-107177/index.md)
```

## Sources

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

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