What is GHSA-PM3M-32R3-7MFH?

GHSA-PM3M-32R3-7MFH is a low-severity security vulnerability in go.etcd.io/etcd/v3 (go), affecting versions >= 3.4.0-rc.0, <= 3.4.9. It is fixed in 3.4.10, 3.3.23.

Which versions of go.etcd.io/etcd/v3 are affected by GHSA-PM3M-32R3-7MFH?

go.etcd.io/etcd/v3 (go) versions >= 3.4.0-rc.0, <= 3.4.9 is affected.

Is there a fix for GHSA-PM3M-32R3-7MFH?

Yes. GHSA-PM3M-32R3-7MFH is fixed in 3.4.10, 3.3.23. Upgrade to this version or later.

Is GHSA-PM3M-32R3-7MFH exploitable, and should I be worried?

Whether GHSA-PM3M-32R3-7MFH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-PM3M-32R3-7MFH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-PM3M-32R3-7MFH in go.etcd.io/etcd/v3

Q: Which versions of go.etcd.io/etcd/v3 are affected by GHSA-PM3M-32R3-7MFH?

go.etcd.io/etcd/v3 (go) versions >= 3.4.0-rc.0, <= 3.4.9 is affected.

Q: Is there a fix for GHSA-PM3M-32R3-7MFH?

Yes. GHSA-PM3M-32R3-7MFH is fixed in 3.4.10, 3.3.23. Upgrade to this version or later.

Q: Is GHSA-PM3M-32R3-7MFH exploitable, and should I be worried?

Whether GHSA-PM3M-32R3-7MFH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-PM3M-32R3-7MFH is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-PM3M-32R3-7MFH?

Upgrade: go.etcd.io/etcd/v3 to 3.4.10 or later, go.etcd.io/etcd/v3 to 3.3.23 or later.

Summary

Etcd embed auto compaction retention negative value causing a compaction loop or a crash

Detail

The parseCompactionRetention function in embed/etcd.go allows the retention variable value to be negative and causes the node to execute the history compaction in a loop, taking more CPU than usual and spamming logs.

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

Impact

Data Validation

Affected versions

go.etcd.io/etcd/v3 (>= 3.4.0-rc.0, <= 3.4.9) go.etcd.io/etcd/v3 (< 3.3.23)

Security releases

go.etcd.io/etcd/v3 → 3.4.10 (go) go.etcd.io/etcd/v3 → 3.3.23 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

go.etcd.io/etcd/v3 to 3.4.10 or later; go.etcd.io/etcd/v3 to 3.3.23 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-PM3M-32R3-7MFH? GHSA-PM3M-32R3-7MFH is a low-severity security vulnerability in go.etcd.io/etcd/v3 (go), affecting versions >= 3.4.0-rc.0, <= 3.4.9. It is fixed in 3.4.10, 3.3.23.
Which versions of go.etcd.io/etcd/v3 are affected by GHSA-PM3M-32R3-7MFH? go.etcd.io/etcd/v3 (go) versions >= 3.4.0-rc.0, <= 3.4.9 is affected.
Is there a fix for GHSA-PM3M-32R3-7MFH? Yes. GHSA-PM3M-32R3-7MFH is fixed in 3.4.10, 3.3.23. Upgrade to this version or later.
Is GHSA-PM3M-32R3-7MFH exploitable, and should I be worried? Whether GHSA-PM3M-32R3-7MFH is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-PM3M-32R3-7MFH is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-PM3M-32R3-7MFH?
- Upgrade go.etcd.io/etcd/v3 to 3.4.10 or later
- Upgrade go.etcd.io/etcd/v3 to 3.3.23 or later

Other vulnerabilities in go.etcd.io/etcd/v3

CVE-IDSeverityPackage summary

CVE-2026-44283Lowgo.etcd.io/etcd/v3: etcd RBAC bypass allows unauthorized data access via PrevKv/lease attachment in nested transaction Put requests CVE-2026-33413Highgo.etcd.io/etcd/v3: etcd: Authorization bypasses in multiple APIs CVE-2026-33343Lowgo.etcd.io/etcd/v3: etcd: Nested etcd transactions bypass RBAC authorization checks GHSA-VJG6-93FV-QV64Lowgo.etcd.io/etcd/v3: Etcd auth Inaccurate logging of authentication attempts for users with CN-based auth only GHSA-J86V-2VJR-FG8FMediumgo.etcd.io/etcd/v3: Etcd Gateway TLS endpoint validation only confirms TCP reachability