CVE-2026-19017

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory published 2026-08-07. a secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

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

Consul Community Edition and Consul Enterprise 1.18.21 through 2.0.2 are vulnerable to a partial arbitrary file read when configured to use the Vault Connect CA provider with JWT or AppRole authentication. A privileged attacker with operator:write permission may direct Consul to read and forward credential files outside the intended scope, potentially leading to the exfiltration of sensitive secrets from the Consul server host. This vulnerability, CVE-2026-19017, is fixed in Consul 2.0.3 and Consul Enterprise 1.21.17, 1.22.11, and 2.0.3.

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

Published

August 7, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
No patch confirmed yet.
generic

HCSEC-2026-25 - Multiple vulnerabilities impacting HashiCorp Consul - Security - HashiCorp Discuss

https://discuss.hashicorp.com/t/hcsec-2026-25-multiple-vulnerabilities-impacting-hashicorp-consul/77629

Vendor Advisories for CVE-2026-19017(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 20× in last 7d / 40× 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-20 01:39 UTCEG score recompute
  2. 2026-08-20 01:39 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 01:19 UTCEG score recompute
  5. 2026-08-19 01:19 UTCGHSA enrichment
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-18 00:56 UTCEG score recompute
  8. 2026-08-18 00:56 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 00:32 UTCEG score recompute
  11. 2026-08-17 00:32 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-16 00:12 UTCEG score recompute
  15. 2026-08-16 00:12 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 23:52 UTCGHSA enrichment
  18. 2026-08-13 23:32 UTCEG score recompute
  19. 2026-08-13 23:32 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 23:11 UTCEG score recompute
  22. 2026-08-12 23:11 UTCGHSA enrichment
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 22:51 UTCEG score recompute
  25. 2026-08-11 22:51 UTCGHSA enrichment
Show 15 more
  1. 2026-08-11 13:42 UTCEPSS rescore
  2. 2026-08-11 00:00 UTCEPSS rescore
  3. 2026-08-10 22:31 UTCEG score recompute
  4. 2026-08-10 22:31 UTCGHSA enrichment
  5. 2026-08-10 21:30 UTCEG score recompute
  6. 2026-08-10 21:30 UTCGHSA enrichment
  7. 2026-08-09 21:10 UTCEG score recompute
  8. 2026-08-09 21:10 UTCGHSA enrichment
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-08 20:50 UTCEG score recompute
  11. 2026-08-08 20:50 UTCGHSA enrichment
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 20:30 UTCEG score recompute
  14. 2026-08-07 19:37 UTCEG score recompute
  15. 2026-08-07 19:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19017?
CVE-2026-19017 is a medium vulnerability published on August 7, 2026. Consul Community Edition and Consul Enterprise 1.18.21 through 2.0.2 are vulnerable to a partial arbitrary file read when configured to use the Vault Connect CA provider with JWT or AppRole authentication. A privileged attacker with operator:write permission may direct Consul to read and forward…
When was CVE-2026-19017 disclosed?
CVE-2026-19017 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19017 actively exploited?
CVE-2026-19017 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 74.2% of all scored CVEs.
What is the CVSS score of CVE-2026-19017?
CVE-2026-19017 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-19017?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19017, 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-19017

Explore →

Is Your Infrastructure Affected by CVE-2026-19017?

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

Start Free Scan →Browse All CVEs