CVE-2026-107177

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-10-07. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
43
EG Risk 43/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 7, 2026

Last Modified

October 7, 2026

Advisory Details (5)

Auto-updated Oct 7, 2026
🔬 Proof of concept available. No fix on record yet.
generic

Express Gateway through 1.16.11 Hardcoded Default cipherKey Exposes OAuth Tokens | Advisories | VulnCheck

https://www.vulncheck.com/advisories/express-gateway-through-1.16.11-hardcoded-default-cipherkey-exposes-oauth-tokens
generic

express-gateway/lib/services/utils.js at 45612814d12f65889ef3bdf80b2ed7ab9b557736 · ExpressGateway/express-gateway · GitHub

https://github.com/ExpressGateway/express-gateway/blob/45612814d12f65889ef3bdf80b2ed7ab9b557736/lib/services/utils.js#L18-L28
generic

express-gateway/lib/config/system.config.yml at 45612814d12f65889ef3bdf80b2ed7ab9b557736 · ExpressGateway/express-gateway · GitHub

https://github.com/ExpressGateway/express-gateway/blob/45612814d12f65889ef3bdf80b2ed7ab9b557736/lib/config/system.config.yml#L15-L22
generic

GitHub - ExpressGateway/express-gateway: A microservices API Gateway built on top of Express.js · GitHub

https://github.com/ExpressGateway/express-gateway
generic🟡 PoC Available

Hard-coded cryptographic secrets shipped in `system.config.yml` (token-encryption key and session-signing key) · Issue #1078 · ExpressGateway/express-gateway · GitHub

https://github.com/ExpressGateway/express-gateway/issues/1078

Vendor Advisories for CVE-2026-107177(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-09 15:01 UTCEG score recompute
  3. 2026-10-09 15:01 UTCGHSA enrichment
  4. 2026-10-08 17:11 UTCEPSS rescore
  5. 2026-10-08 16:43 UTCGHSA enrichment
  6. 2026-10-07 18:39 UTCEG score recompute
  7. 2026-10-07 18:39 UTCGHSA enrichment
  8. 2026-10-07 17:47 UTCEG score recompute
  9. 2026-10-07 17:47 UTCGHSA enrichment
  10. 2026-10-07 16:13 UTCEG score recompute
  11. 2026-10-07 16:12 UTCGHSA enrichment
  12. 2026-10-07 13:25 UTCEG score recompute
  13. 2026-10-07 13:02 UTCEG score recompute
  14. 2026-10-07 13:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-107177?
CVE-2026-107177 is a medium vulnerability published on October 7, 2026. 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…
When was CVE-2026-107177 disclosed?
CVE-2026-107177 was first published on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-107177 actively exploited?
CVE-2026-107177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-107177?
CVE-2026-107177 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-107177?
No fix for CVE-2026-107177 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-107177 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-107177

Explore →

Is Your Infrastructure Affected by CVE-2026-107177?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs