CVE-2026-107177

waiting for further signalsZero needs more public information before it can validate it.

GHSA-rq2q-fwh6-p47r ↗EUVD-2026-94317 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
ExpressGateway express-gateway <= 1.16.11
CWE-1394 Use of Default Cryptographic Key
ETK-2026-874, permanent identifier
14d 03h 35msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h36m
0
+4h
+6h
+8h
+10h
+12h

description

Express Gateway through 1.16.11 uses a known default key for encrypting stored OAuth token secrets. An attacker with datastore read access, including Redis access, may decrypt those secrets and use stored token identifiers to obtain bearer tokens for users.

mitigation

Replace the default crypto.cipherKey with a unique protected value, restrict datastore and Redis read access, and rotate potentially exposed OAuth tokens. No fixed version is recorded in the advisory.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.32%23rd percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 12:48Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-07 12:48Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-107177

{
  "etk_id": "ETK-2026-874",
  "cve_id": "CVE-2026-107177",
  "display_id": "CVE-2026-107177",
  "ghsa_id": "GHSA-rq2q-fwh6-p47r",
  "euvd_id": "EUVD-2026-94317",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hardcoded cryptographic key in Express Gateway",
  "summary": "Express Gateway through 1.16.11 uses a known default key for encrypting stored OAuth token secrets. An attacker with datastore read access, including Redis access, may decrypt those secrets and use stored token identifiers to obtain bearer tokens for users.",
  "mitigation": "Replace the default `crypto.cipherKey` with a unique protected value, restrict datastore and Redis read access, and rotate potentially exposed OAuth tokens. No fixed version is recorded in the advisory.",
  "vendor": "ExpressGateway",
  "product": "express-gateway",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.16.11"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "express-gateway",
      "purl": null
    }
  ],
  "cwes": [
    1394
  ],
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0032,
  "epss_percentile": 0.2308,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.754842933333332,
  "t0_at": "2026-10-07T12:48:19.043000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T12:48:19.043000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T12:48:19.043000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107177"
    }
  }
}

published 2026-10-07 14:05Z
last change 2026-10-21 17:47Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.