CVE-2026-73499 etcd-io CVE debrief

Who should care

Defenders and administrators of etcd clusters with authentication enabled should assess exposure and apply patches if necessary. They should also review cluster authentication settings and monitor watch events for unusual activity. Security teams should prioritize verifying exposure and applying patches for etcd versions prior to 3.5.33, 3.6.14, and 3.7.1.

Why it matters

CVE-2026-73499 allows users with READ permission to access watch events beyond their intended scope in etcd clusters with authentication enabled. Defenders should verify exposure, apply patches, and monitor cluster activity.

• Potential unauthorized access to sensitive data through watch events
• Possible disruption of etcd cluster operations
• Need for verification of etcd version and cluster authentication settings
• Requirement for monitoring watch events for unusual activity

Technical summary

The vulnerability in etcd allows users with READ permission on a single exact key to receive watch events for every key lexicographically greater than or equal to the permitted key. This issue affects clusters with authentication enabled. The vulnerability is fixed in etcd versions 3.5.33, 3.6.14, and 3.7.1. Defenders should prioritize verifying exposure and applying patches for etcd versions prior to 3.5.33, 3.6.14, and 3.7.1 in clusters with authentication enabled. The issue can be mitigated by reviewing compensating controls for exposed systems while remediation is scheduled and verified.

Defensive priority

Defenders should prioritize verifying exposure and applying patches for etcd versions prior to 3.5.33, 3.6.14, and 3.7.1 in clusters with authentication enabled.

Recommended defensive actions

• Verify etcd version and apply patches if necessary
• Review cluster authentication settings
• Monitor watch events for unusual activity
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The issue is described in the CVE record and NVD vulnerability detail page. Fixes are provided in etcd versions 3.5.33, 3.6.14, and 3.7.1. Defenders should verify exposure by reviewing cluster authentication settings and etcd version. They should also monitor watch events for unusual activity and apply patches if necessary. The vulnerability allows users with READ permission on a single exact key to receive watch events for every key lexicographically greater than or equal to the permitted key.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.