Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
LOW severity

GHSA-p4g4-wgrh-qrg2 — etcd

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.

Panic due to malformed WALs in go.etcd.io/etcd

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

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-p4g4-wgrh-qrg2 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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

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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p4g4-wgrh-qrg2 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p4g4-wgrh-qrg2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-p4g4-wgrh-qrg2 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-p4g4-wgrh-qrg2: etcd (Low 3.7) | O3 Security