CVE-2026-16328

HIGHPre-NVD 8.68.6—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

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

In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address was supplied, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect the server's Consul API traffic to an attacker-controlled endpoint, potentially exfiltrating the Consul token configured on the server. This vulnerability, CVE-2026-16328, is fixed in consul-mcp-server 0.1.4.

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
43(Track)
EG Risk 43/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
Severity86% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 29, 2026
No patch confirmed yet.
generic

HCSEC-2026-24 - Multiple vulnerabilities impacting HashiCorp Consul MCP Server - Security - HashiCorp Discuss

https://discuss.hashicorp.com/t/hcsec-2026-24-multiple-vulnerabilities-impacting-hashicorp-consul-mcp-server/77612

Vendor Advisories for CVE-2026-16328(2)

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 12× in last 7d / 12× 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-08-01 05:35 UTCEG score recompute
  2. 2026-08-01 05:35 UTCGHSA enrichment
  3. 2026-08-01 04:15 UTCEPSS rescore
  4. 2026-07-31 16:36 UTCGHSA enrichment
  5. 2026-07-31 03:36 UTCEG score recompute
  6. 2026-07-31 03:36 UTCGHSA enrichment
  7. 2026-07-30 14:38 UTCGHSA enrichment
  8. 2026-07-30 09:20 UTCEG score recompute
  9. 2026-07-30 09:20 UTCGHSA enrichment
  10. 2026-07-29 19:32 UTCEG score recompute
  11. 2026-07-29 18:53 UTCEG score recompute
  12. 2026-07-29 18:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16328?
CVE-2026-16328 is a high vulnerability published on July 29, 2026. In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address was supplied, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect the server's Consul API traffic to an…
When was CVE-2026-16328 disclosed?
CVE-2026-16328 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16328 actively exploited?
CVE-2026-16328 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.8% of all scored CVEs.
What is the CVSS score of CVE-2026-16328?
CVE-2026-16328 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-16328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16328, 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-16328

Explore →

Is Your Infrastructure Affected by CVE-2026-16328?

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

Start Free Scan →Browse All CVEs