CVE-2026-16326

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 10.0Exploit: 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 properly isolate session state in stateless mode, which may allow one client's Consul authentication token to be used for subsequent requests from other clients. This vulnerability (CVE-2026-16326) is fixed in consul-mcp-server 0.1.4.

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

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (1)

Auto-updated Jul 30, 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-16326(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 23× in last 7d / 23× 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 06:58 UTCEG score recompute
  2. 2026-08-01 06:58 UTCGHSA enrichment
  3. 2026-08-01 04:15 UTCEPSS rescore
  4. 2026-08-01 02:55 UTCGHSA enrichment
  5. 2026-07-31 22:52 UTCGHSA enrichment
  6. 2026-07-31 18:50 UTCGHSA enrichment
  7. 2026-07-31 14:48 UTCGHSA enrichment
  8. 2026-07-31 10:46 UTCGHSA enrichment
  9. 2026-07-31 06:44 UTCGHSA enrichment
  10. 2026-07-31 02:44 UTCGHSA enrichment
  11. 2026-07-30 22:43 UTCGHSA enrichment
  12. 2026-07-30 18:45 UTCEG score recompute
  13. 2026-07-30 18:44 UTCGHSA enrichment
  14. 2026-07-30 14:38 UTCGHSA enrichment
  15. 2026-07-30 12:19 UTCEG score recompute
  16. 2026-07-30 12:19 UTCGHSA enrichment
  17. 2026-07-30 08:20 UTCGHSA enrichment
  18. 2026-07-30 04:20 UTCGHSA enrichment
  19. 2026-07-30 00:21 UTCEG score recompute
  20. 2026-07-30 00:21 UTCGHSA enrichment
  21. 2026-07-29 19:32 UTCEG score recompute
  22. 2026-07-29 18:53 UTCEG score recompute
  23. 2026-07-29 18:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16326?
CVE-2026-16326 is a critical vulnerability published on July 29, 2026. In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not properly isolate session state in stateless mode, which may allow one client's Consul authentication token to be used for subsequent requests from other clients. This vulnerability (CVE-2026-16326) is fixed in consul-mcp-server 0.1.4.
When was CVE-2026-16326 disclosed?
CVE-2026-16326 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-16326 actively exploited?
CVE-2026-16326 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 77.8% of all scored CVEs.
What is the CVSS score of CVE-2026-16326?
CVE-2026-16326 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-16326?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16326, 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-16326

Explore →

Is Your Infrastructure Affected by CVE-2026-16326?

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

Start Free Scan →Browse All CVEs