CVE-2023-32082 is a low-severity (CVSS 3.1) Information Exposure vulnerability in github.com/etcd-io/etcd. A fix is available for github.com/etcd-io/etcd — see the affected versions and patch details below.
etcd key name can be accessed via LeaseTimeToLive API
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-32082.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/etcd-io/etcd🐹github.com/etcd-io/etcdReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.26 and 3.5.9, the LeaseTimeToLive API allows access to key names (not value) associated to a lease when Keys parameter is true, even a user doesn't have read permission to the keys. The impact is limited to a cluster which enables auth (RBAC). Versions 3.4.26 and 3.5.9 fix this issue. There are no known workarounds.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/etcd-io/etcd | all versions | 3.4.26go get github.com/etcd-io/etcd@v3.4.26 |
| 🐹Go | github.com/etcd-io/etcd | ≥ 3.5.0&&< 3.5.9 | 3.5.9go get github.com/etcd-io/etcd@v3.5.9 |
Affected Products
etcdetcdDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/etcd-io/etcd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/etcd-io/etcd to 3.4.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-32082 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 17.0 | etcd-0:3.4.26-1.el9ost | RHSA-2023:3441 |
Frequently Asked Questions
Is CVE-2023-32082 in your dependencies?
Find it across Go, including transitive dependencies.