etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows. Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice. Restrict network access to etcd server ports so only trusted components can connect and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.

An update of the etcd package has been released.

The version of CBL-Mariner Releases installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2026-33413 advisory.

  - etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42,     3.5.28, and 3.6.9, unauthorized users May bypass authentication or authorization checks and call certain     etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In     unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn     cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for     operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease     ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch,     audit, and recovery workflows. Kubernetes does not rely on etcd's built-in authentication and     authorization. Instead, the API server handles authentication and authorization itself, so typical     Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading     is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice.
    Restrict network access to etcd server ports so only trusted components can connect and/or require strong     client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
    (CVE-2026-33413)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of CBL-Mariner Releases installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2026-33413 advisory.

  - etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42,     3.5.28, and 3.6.9, unauthorized users May bypass authentication or authorization checks and call certain     etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In     unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn     cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for     operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease     ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch,     audit, and recovery workflows. Kubernetes does not rely on etcd's built-in authentication and     authorization. Instead, the API server handles authentication and authorization itself, so typical     Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading     is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice.
    Restrict network access to etcd server ports so only trusted components can connect and/or require strong     client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
    (CVE-2026-33413)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42,     3.5.28, and 3.6.9, unauthorized users may bypass authentication or authorization checks and call certain     etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients. In     unpatched etcd clusters with etcd auth enabled, unauthorized users are able to call MemberList and learn     cluster topology, including member IDs and advertised endpoints; call Alarm, which can be abused for     operational disruption or denial of service; use Lease APIs, interfering with TTL-based keys and lease     ownership; and/or trigger compaction, permanently removing historical revisions and disrupting watch,     audit, and recovery workflows. Kubernetes does not rely on etcd's built-in authentication and     authorization. Instead, the API server handles authentication and authorization itself, so typical     Kubernetes deployments are not affected. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. If upgrading     is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice.
    Restrict network access to etcd server ports so only trusted components can connect and/or require strong     client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
    (CVE-2026-33413)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
306492	Photon OS 5.0: Etcd PHSA-2026-5.0-0802	Nessus	PhotonOS Local Security Checks	high
304498	CBL Mariner 2.0 Security Update: CBL-Mariner Releases (CVE-2026-33413)	Nessus	MarinerOS Local Security Checks	high
304372	Azure Linux 3.0 Security Update: CBL-Mariner Releases (CVE-2026-33413)	Nessus	Azure Linux Local Security Checks	high
303898	Linux Distros Unpatched Vulnerability : CVE-2026-33413	Nessus	Misc.	high

Detections

Analytics

CVE-2026-33413

high

Tenable Plugins

high

high

high

high