CVE-2026-91164

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.3Exploit: None knownExposed: 0

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

Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. From 0.23.0 until 0.27.3, HTTP API token authentication resolves ConfigProvider::validate_api_token into RequestAuthorization::UserToken without enforcing the owning user's allowed_ip_ranges against the trusted client address in warpgate-protocol-http/src/common.rs. An attacker holding a leaked, phished, or exfiltrated X-Warpgate-Token can therefore use it from a prohibited network location. Deployments without allowed_ip_ranges are unaffected, and HTTP target proxying plus SSH, MySQL, PostgreSQL, RDP, VNC, and Kubernetes paths do not accept this vulnerable HTTP token flow. This issue is fixed in version 0.27.3.

CVSS v3
4.3
EG Score
4.3(low)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 21, 2026

Last Modified

September 21, 2026

Advisory Details (4)

Auto-updated Sep 21, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v0.27.3

Patch available: warp-tech/warpgate v0.27.3

https://github.com/warp-tech/warpgate/releases/tag/v0.27.3
github_commit

commit 8cb33a1a7c44 (warp-tech/warpgate)

Fix landed in warp-tech/warpgate commit 8cb33a1a7c44 — awaiting tagged release

https://github.com/warp-tech/warpgate/commit/8cb33a1a7c447ab0cde3a1ee9f95bf9dde905482
github_pr

request validation for tokens

Fix merged in warp-tech/warpgate PR #2356 on 2026-08-04 — awaiting tagged release

https://github.com/warp-tech/warpgate/pull/2356
github Patch Available

API tokens bypass the user's allowed_ip_ranges restriction · Advisory · warp-tech/warpgate · GitHub

Affected: 0.27.3. validate_api_token now takes the request's trusted client IP and applies

https://github.com/warp-tech/warpgate/security/advisories/GHSA-qmr2-wp96-h9ff

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 4× 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-09-21 20:18 UTCEG score recompute
  2. 2026-09-21 19:21 UTCEG score recompute
  3. 2026-09-21 18:55 UTCEG score recompute
  4. 2026-09-21 18:55 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-91164?
CVE-2026-91164 is a medium vulnerability published on September 21, 2026. Warpgate is an open source SSH, HTTPS and MySQL bastion host for Linux. From 0.23.0 until 0.27.3, HTTP API token authentication resolves ConfigProvider::validateapitoken into RequestAuthorization::UserToken without enforcing the owning user's allowedipranges against the trusted client address in…
When was CVE-2026-91164 disclosed?
CVE-2026-91164 was first published in the National Vulnerability Database on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-91164?
CVE-2026-91164 has a CVSS v3 base score of 4.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-91164?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91164, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-91164?

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

Start Free Scan →Browse All CVEs