Advisory record · GHSA-x35m-3gp4-4fh5

etcd RBAC bypass allows unauthorized data access via PrevKv/lease attachment in nested transaction Put requests

CVSS 0.0 NoneEPSS 0.0022 · 13th percentile

Published by the GitHub Advisory Database at 7 May 2026, 03:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
go.etcd.io/etcd/v3Go>=3.6.0, <3.6.11 || >=3.5.0, <3.5.303.6.11, 3.5.30
go.etcd.io/etcdGo<3.4.443.4.44
Identifiers
GHSA-x35m-3gp4-4fh5 · BIT-etcd-2026-44283 · CVE-2026-44283 · GO-2026-5736
Weakness (CWE)
CWE-863
Published
7 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of etcd go.etcd.io/etcd/v3 from 3.5.0 before 3.5.30 and from 3.6.0 before 3.6.11, and go.etcd.io/etcd before 3.4.44, have an RBAC bypass in transaction Put requests. An authenticated user lacking sufficient read or lease permissions can use the PrevKv option or attach a lease within a transaction to access unauthorized data or attach leases. Upgrade to 3.5.30, 3.6.11, or 3.4.44 as applicable. Restricting network access to etcd ports to trusted components, or requiring mTLS client certificates, reduces exposure until upgrade.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
0.0 None 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 13th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 14 May 2026, 18:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:13 UTC First seen by agentprime
  3. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.