etcd's WAL ReadAll method vulnerable to an entry with large index causing panic

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2020-15112: 1.26% estimated exploitation activity in the next 30 days; percentile 69.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Vulnerability type Data Validation Detail In the ReadAll method in wal/wal.go, it is possible to have an entry index greater then the number of entries. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry. References Find out more on this vulnerability in the security audit report For more information If you have any questions or comments about this advisory: Contact the etcd security committee

Published by the source

6 Oct 2022, 23:03 UTC

Last modified by the source

15 Feb 2023, 19:25 UTC

Source last checked

26 Oct 2026, 14:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m332-53r6-2w93

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-15112

Advisory: etcd's WAL `ReadAll` method vulnerable to an entry with large index causing panic
IDs: CVE-2020-15112, GHSA-m332-53r6-2w93
Record: https://patchnext.com/advisories/cve-2020-15112 (revision 1, source checked 26 Oct 2026, 14:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.etcd.io/etcd/v3 3.4.10, 3.3.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.etcd.io/etcd/v3: affected < 3.3.23; >= 3.4.0, < 3.4.10; fixed in 3.3.23, 3.4.10

## Suggested inspection (read-only)
- Go go.etcd.io/etcd/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.etcd.io/etcd/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m332-53r6-2w93 (GitHub-reviewed advisory GHSA-m332-53r6-2w93 lists affected ranges: Go go.etcd.io/etcd/v3 >=0 =3.4.0 <3.4.10)

Commands are suggestions: review each one before running it.