etcd-io
etcd
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at etcd, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-73500 | 12 Aug 2026 | etcd: < 3.5.33, >= 3.6.0, < 3.6.14, >= 3.7.0-alpha.0, < 3.7.1 | For more details, see the Red Hat Advanced Cluster Management for Kubernetes documentation: https://docs.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.13/html/multicluster_global_hub/index | Update reference ↗ |
| CVE-2026-73499 | 12 Aug 2026 | etcd: < 3.5.33, >= 3.6.0, < 3.6.14, >= 3.7.0-alpha.0, < 3.7.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-59818 | 8 Jul 2026 | >= 3.6.0-alpha.0, < 3.6.13; < 3.5.32 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-44283 | 14 May 2026 | < 3.4.44; >= 3.5.0, <= 3.5.29; >= 3.6.0, <= 3.6.10 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ | Update reference ↗ |
| CVE-2026-33413 | 26 Mar 2026 | >= 3.6.0-alpha.0, < 3.6.9; >= 3.5.0-alpha.0, < 3.5.28; < 3.4.42 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-33343 | 26 Mar 2026 | >= 3.5.0-alpha.0, < 3.5.28; >= 3.6.0-alpha.0, < 3.6.9; < 3.4.42 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-32082 | 11 May 2023 | < 3.4.26; >= 3.5.0, < 3.5.9 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-15136 | 6 Aug 2020 | >= 3.4.0, < 3.4.10; < 3.3.23 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-15114 | 6 Aug 2020 | < 3.3.23; < 3.4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-15115 | 6 Aug 2020 | < 3.3.23; < 3.4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-15112 | 5 Aug 2020 | < 3.3.23; < 3.4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-15113 | 5 Aug 2020 | < 3.3.23; < 3.4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2020-15106 | 5 Aug 2020 | < 3.3.23; < 3.4.10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.