Skip to main content
VulnerabilityPublished

CVE-2026-59818: etcd · Improper Certificate Validation

Affects etcdSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.6.13 or 3.5.32 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.13, 3.5.32
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade etcd and etcd-io/etcd to 3.6.13 or 3.5.32.

Affected software

ProductAffectedFixed in
etcd-ioetcdAffected
  • >=3.6.0-alpha.0 <3.6.13
Fixed in
  • 3.6.13
etcd-ioetcdAffected
  • <3.5.32
Fixed in
  • 3.5.32
GitHubetcd-io/etcdpkg:github/etcd-io/etcdOther threatsAffected
  • <3.5.32
  • <3.6.13
Fixed in
  • 3.5.32
  • 3.6.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade etcd to version 3.5.32 or 3.6.13 or later, where the enforcement of the client CRL on the gRPC listener is fixed. No other mitigation or temporary workaround is indicated in the available data.

Description

etcd is a distributed key-value store for the data of a distributed system. Prior to 3.5.32 and 3.6.13, when etcd is configured with --listen-client-http-urls to split HTTP and gRPC client endpoints onto separate listeners, the --client-crl-file Certificate Revocation List is not enforced on the gRPC listener, allowing a client with a revoked certificate to authenticate successfully over gRPC. This issue is fixed in versions 3.5.32 and 3.6.13.

References

Community reviews

Loading reviews…