Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

etcd: Read access via PrevKv in etcd transactions may bypass RBAC authorization checks

CVSS 3.1 0.0 NONEeuvd · severity unknownCVSS 3.1 · [email protected] · Secondary 0.0 NONECVSS 3.1 · [email protected] · Primary 4.3 MEDIUMCVSS_V3 Publisher rating LOWFixed by go.etcd.io/etcd/v3 3.6.11Fixed by go.etcd.io/etcd/v3 3.5.30Fixed by go.etcd.io/etcd 3.4.44osv · severity unknownFixed by go.etcd.io/etcd/server/v3 3.5.30Fixed by go.etcd.io/etcd/server/v3 3.6.11KEV status unknown

cve-program · CVE-2026-44283

Published

etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.

Read the publisher's advisory

euvd · EUVD-2026-30345

Published

etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.

Read the publisher's advisory

nvd · CVE-2026-44283

Published

etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.

Read the publisher's advisory

osv · GHSA-x35m-3gp4-4fh5

Published

### Impact _What kind of vulnerability is it? Who is impacted?_ A vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. 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. ### Patches _Has the problem been patched? What versions should users upgrade to?_ This vulnerability is patched in the following versions: - etcd 3.6.11 - etcd 3.5.30 - etcd 3.4.44 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ 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 - require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution ### Reporters Samy Ghannad (@SamyGhannad on Github) reported that read access via PrevKv in a Put request within etcd transactions bypassed RBAC authorization checks. Benjamin Wang (@ahrtr ) further analyzed that lease attachment in a Put request within etcd transactions also bypassed RBAC authorization checks

Read the publisher's advisory

osv · GO-2026-5736

Published

Etcd RBAC bypass via PrevKv/lease in nested transactions in go.etcd.io/etcd/v3 in go.etcd.io/etcd/server

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-44283

Published

etcd

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "etcd-io",
                    "product": "etcd",
                    "versions": [
                        {
                            "version": "< 3.4.44",
                            "status": "affected"
                        },
                        {
                            "version": ">= 3.5.0, <= 3.5.29",
                            "status": "affected"
                        },
                        {
                            "version": ">= 3.6.0, <= 3.6.10",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-30345

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: May 14, 2026, 5:01:33 PM

dateUpdated: May 16, 2026, 12:40:51 AM

4 related source bulletins · separate from aliases

openSUSE-SU-2026:10980-1: flannel-0.28.5-1.1 on GA media

CVE-2026-44283

RHSA-2026:44868: Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

CVE-2026-44283 · CVE-2026-59818 · CVE-2026-73500

msrc_CVE-2026-44283: etcd: Read access via PrevKv in etcd transactions may bypass RBAC authorization checks

CVE-2026-44283

WID-SEC-W-2026-1400: etcd: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

CVE-2026-44283

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-44283

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-863

Original publisher date fields

published: 2026-05-14T18:16:49.650

lastModified: 2026-11-11T20:10:00.273

1 source CPE criteria · context only
  • cpe:2.3:a:etcd:etcd:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-x35m-3gp4-4fh5

Published

go.etcd.io/etcd/v3

Go

SEMVER · introduced 3.6.0 → fixed 3.6.11

go.etcd.io/etcd/v3

Go

SEMVER · introduced 3.5.0 → fixed 3.5.30

go.etcd.io/etcd

Go

SEMVER · introduced 0 → fixed 3.4.44

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-5736

Published

go.etcd.io/etcd/server/v3

Go

SEMVER · introduced 3.5.0 → fixed 3.5.30 → introduced 3.6.0 → fixed 3.6.11

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 01:32 UTC · 272 of 275 readable · 250 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current