Security Deep Dive
etcd
Security posture and CVE patch evidence from tracked releases.
1 actively-exploited dependency CVE affects v3.6.12.
KEV-listed CVEs are confirmed exploited in the wild — patch urgently.
Versions by Severity
CVEs are attributed to tracked releases published before the patch release.
| Version | Published | C | H | M | L | KEV | Notes |
|---|---|---|---|---|---|---|---|
| v3.6.12 | 2026-06-01 | — | — | — | — | — |
Latest
|
| v3.5.31 | 2026-06-01 | — | — | — | — | — |
—
|
| v3.4.45 | 2026-06-01 | — | — | — | — | — |
Patches
CVE-2023-44487
|
| v3.6.11 | 2026-05-01 | — | 1 | — | — | KEV 1 |
—
|
| v3.5.30 | 2026-05-01 | — | 1 | — | — | KEV 1 |
—
|
| v3.4.44 | 2026-05-01 | — | 1 | — | — | KEV 1 |
—
|
| v3.6.10 | 2026-04-01 | — | 1 | — | — | KEV 1 |
—
|
| v3.5.29 | 2026-04-01 | — | 1 | — | — | KEV 1 |
—
|
| v3.4.43 | 2026-04-01 | — | 1 | — | — | KEV 1 |
—
|
| v3.6.9 | 2026-03-20 | — | 1 | — | — | KEV 1 |
—
|
| v3.5.28 | 2026-03-20 | — | 1 | — | — | KEV 1 |
—
|
| v3.4.42 | 2026-03-20 | — | 1 | — | — | KEV 1 |
—
|
| v3.6.8 | 2026-02-13 | — | 1 | — | — | KEV 1 |
—
|
| v3.5.27 | 2026-02-13 | — | 1 | — | — | KEV 1 |
—
|
| v3.4.41 | 2026-02-13 | — | 1 | — | — | KEV 1 |
—
|
| v3.6.7 | 2025-12-17 | — | 1 | — | — | KEV 1 |
—
|
| v3.5.26 | 2025-12-17 | — | 1 | — | — | KEV 1 |
—
|
| v3.4.40 | 2025-12-17 | — | 1 | — | — | KEV 1 |
—
|
| v3.6.6 | 2025-11-12 | — | 1 | — | — | KEV 1 |
—
|
| v3.5.25 | 2025-11-12 | — | 1 | — | — | KEV 1 |
—
|
Trust Signals — 2 of 9 Present
Evidence already collected from releases and repository metadata.
Security Score
A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.
epss
0.00 / 0.5
Max EPSS 0.944
freshness
1.00 / 1.0
Up to date
scorecard
2.52 / 4.0
Score 6.3/10
cve health
0.00 / 2.5
⚠ No direct scan — 2c/9h transitive CVEs
patch speed
0.50 / 0.5
⚠ Estimated — no CVE patch history
kev exposure
-1.50 / 1.5
KEV exposure detected
supply chain risk
-1.50 / 10.0
Risk 41.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.9
10%
Provenance trust
provenance trust
6.3
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
0.0
10%
How is this calculated?
The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.
Supply Chain Risk
Risk 41.0/100Scorecard
Scorecard 6.3/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 10 | all changesets reviewed |
| Dependency-Update-Tool | 10 | update tool detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 9 | security policy file detected |
| Maintained | 10 | 30 commit(s) and 22 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 0 | dangerous workflow patterns detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| CII-Best-Practices | 5 | badge detected: Passing |
| License | 10 | license file detected |
| Pinned-Dependencies | 6 | dependency not pinned by hash detected -- score normalized to 6 |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Fuzzing | 10 | project is fuzzed |
| Branch-Protection | -1 | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| Packaging | 10 | packaging workflow detected |
| Vulnerabilities | 0 | 19 existing vulnerabilities detected |
| SAST | 10 | SAST tool is run on all commits |
| CI-Tests | 10 | 16 out of 16 merged PRs checked by a CI test -- score normalized to 10 |
| Contributors | 10 | project has 36 contributing companies or organizations |
CVE Patch History
Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.
CVEs Patched by Year
| CVE | Severity | EPSS | Disclosed | Fixed in | Days to fix | vs Ecosystem Median | KEV |
|---|---|---|---|---|---|---|---|
| CVE-2023-44487 | HIGH | 99%ile | — | v3.4.45 | — | — | KEV |
KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
2
High
9
Medium
10
Low
0
Unknown
8
1 dependency vulnerabilities are in KEV.
CISA confirmed these vulnerabilities are actively exploited. Treat as critical priority.
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2024-45337 | critical | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2026-33186 | critical | — | google.golang.org/grpc | 1.38.0 | v3.4.45 |
| CVE-2021-43565 | high | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2022-21698 | high | — | github.com/prometheus/client_golang | 1.11.0 | v3.4.45 |
| CVE-2022-27191 | high | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2022-27664 | high | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2022-41723 | high | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2023-39325 | high | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2025-22869 | high | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2025-65637 | high | — | github.com/sirupsen/logrus | 1.8.1 | v3.4.45 |
| GHSA-m425-mq94-257g | high | — | google.golang.org/grpc | 1.38.0 | v3.4.45 |
| CVE-2022-29526 | medium | — | golang.org/x/sys | 0.0.0-20210603125802-9665404d3644 | v3.4.45 |
| CVE-2022-41717 | medium | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2023-3978 | medium | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2023-44487 | medium | KEV | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.5.31 |
| CVE-2023-45288 | medium | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2023-48795 | medium | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2025-22870 | medium | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2025-22872 | medium | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2025-47914 | medium | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2025-58181 | medium | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2021-44716 | unknown | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2022-30636 | unknown | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2024-45338 | unknown | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2025-47911 | unknown | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2025-47913 | unknown | — | golang.org/x/crypto | 0.0.0-20210513164829-c07d793c2f9a | v3.4.45 |
| CVE-2025-58190 | unknown | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| CVE-2026-33814 | unknown | — | golang.org/x/net | 0.0.0-20210525063256-abc453219eb5 | v3.4.45 |
| GO-2023-2153 | unknown | — | google.golang.org/grpc | 1.38.0 | v3.4.45 |
Showing 29 of 29