NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
LOW severity

Panic due to malformed WALs in go.etcd.io/etcdGHSA-p4g4-wgrh-qrg2

LOWFix: etcd-io/etcd#11793

GHSA-p4g4-wgrh-qrg2 is a low-severity (CVSS 3.7) Improper Input Validation vulnerability in go.etcd.io/etcd. A fix is available for go.etcd.io/etcd — see the affected versions and patch details below.

Also known asBIT-etcd-2020-15106BIT-etcd-2020-15112CVE-2020-15106CVE-2020-15112GHSA-m332-53r6-2w93GO-2020-0005
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk-0.03%
Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk
0.00%0.60%1.19%1.79%0.1%1.3%May 26Aug 26Nov 26

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

1 pkg affected
🐹go.etcd.io/etcd

Real-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

Vulnerability type

Data Validation

Detail

The size of a record is stored in the length field of a WAL file and no additional validation is done on this data. Therefore, it is possible to forge an extremely large frame size that can unintentionally panic at the expense of any RAFT participant trying to decode the WAL.

Specific Go Packages Affected

github.com/etcd-io/etcd/wal

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:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogo.etcd.io/etcdall versions0.5.0-alpha.5.0.20200423152442-f4b650b51dc4go get go.etcd.io/etcd@v0.5.0-alpha.5.0.20200423152442-f4b650b51dc4

Affected Products

2 products · 3 configurations
Application
etcdetcd
≥ 3.4.0 && < 3.4.10
range
OS
fedorafedoraproject
1 version
32

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.etcd.io/etcd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update go.etcd.io/etcd to 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p4g4-wgrh-qrg2 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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.

Red HatModerate

* In Red Hat OpenShift Container Platform (RHOCP), the affected components are behind OpenShift OAuth authentication. This restricts access to the vulnerable etcd to authenticated users only. * In Red Hat OpenStack Platform (RHOSP), the use of etcd is limited to the internal API network, which is not accessible to…

ProductFixed inAdvisory
Red Hat Enterprise Linux 7 Extrasetcd-0:3.2.32-1.el7_9RHSA-2021:1407
Red Hat OpenShift Container Platform 4.8openshift4/ose-etcd:v4.8.0-202106152230.p0.git.aefa6bf.assembly.streamRHSA-2021:2438
Red Hat OpenStack Platform 16.1etcd-0:3.3.23-1.el8ostRHSA-2021:0916

Frequently Asked Questions

### Vulnerability type Data Validation ### Detail The size of a record is stored in the length field of a WAL file and no additional validation is done on this data. Therefore, it is possible to forge an extremely large frame size that can unintentionally panic at the expense of any RAFT participant trying to decode the WAL. ### Specific Go Packages Affected github.com/etcd-io/etcd/wal ### References Find out more on this vulnerability in the [security audit report](https://github.com/etcd-io/etcd/blob/master/security/SECURITY_AUDIT.pdf) ### For more information If you have any questions o
O3 Security · Impact-Aware SCA

Is GHSA-p4g4-wgrh-qrg2 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Panic due to malformed WALs in go.etcd.io/etcd (Low 3.7)