Security Deep Dive
tidb
Security posture and CVE patch evidence from tracked releases.
2 critical dependency CVEs affects v8.5.6.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 4 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.25 / 0.5
No EPSS data
freshness
1.00 / 1.0
Up to date
scorecard
2.68 / 4.0
Score 6.7/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
No KEV exposure
supply chain risk
-1.50 / 10.0
Risk 26.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
7.4
10%
Provenance trust
provenance trust
6.7
40%
Maintainer health
maintainer health
10.0
10%
Operational risk
operational risk
8.5
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 26.0/100Scorecard
Scorecard 6.7/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Packaging | -1 | packaging workflow not detected |
| Maintained | 10 | 30 commit(s) and 21 issue activity found in the last 90 days -- score normalized to 10 |
| Code-Review | 10 | all changesets reviewed |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 10 | security policy file detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| License | 10 | license file detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Signed-Releases | -1 | no releases found |
| Fuzzing | 10 | project is fuzzed |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
| Pinned-Dependencies | 2 | dependency not pinned by hash detected -- score normalized to 2 |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
OpenSSF Badge
Badge indicates adherence to open-source best practices.
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
2
High
9
Medium
7
Low
4
Unknown
8
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2022-3023 | critical | — | github.com/pingcap/tidb | 1.1.0-beta.0.20201020170636-b71b6323fd4d | — |
| CVE-2026-33186 | critical | — | google.golang.org/grpc | v1.75.1 | — |
| CVE-2020-15114 | high | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| CVE-2026-24051 | high | — | go.opentelemetry.io/otel/sdk | v1.37.0 | — |
| CVE-2026-29181 | high | — | go.opentelemetry.io/otel | v1.37.0 | — |
| CVE-2026-33413 | high | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| CVE-2026-39883 | high | — | go.opentelemetry.io/otel/sdk | v1.37.0 | — |
| CVE-2026-41602 | high | — | github.com/apache/thrift | v0.21.0 | — |
| CVE-2026-42151 | high | — | github.com/prometheus/prometheus | v0.50.1 | — |
| CVE-2026-42154 | high | — | github.com/prometheus/prometheus | v0.50.1 | — |
| GHSA-m425-mq94-257g | high | — | google.golang.org/grpc | 1.26.0 | — |
| CVE-2018-1099 | medium | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| CVE-2020-15136 | medium | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| CVE-2024-37820 | medium | — | github.com/pingcap/tidb | 1.1.0-beta.0.20201020170636-b71b6323fd4d | — |
| CVE-2026-40179 | medium | — | github.com/prometheus/prometheus | v0.50.1 | — |
| GHSA-fw8g-cg8f-9j28 | medium | — | github.com/prometheus/prometheus | v0.50.1 | — |
| GHSA-xmrv-pmrh-hhx2 | medium | — | github.com/aws/aws-sdk-go-v2/service/s3 | v1.87.1 | — |
| GHSA-xmrv-pmrh-hhx2 | medium | — | github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream | v1.7.0 | — |
| CVE-2020-15106 | low | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| CVE-2026-26958 | low | — | filippo.io/edwards25519 | v1.1.0 | — |
| CVE-2026-33343 | low | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| CVE-2026-44283 | low | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| CVE-2020-8911 | unknown | — | github.com/aws/aws-sdk-go | v1.55.7 | — |
| CVE-2020-8912 | unknown | — | github.com/aws/aws-sdk-go | v1.55.7 | — |
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.52.0 | — |
| GO-2023-2153 | unknown | — | google.golang.org/grpc | 1.26.0 | — |
| GO-2024-2527 | unknown | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| GO-2024-2528 | unknown | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| GO-2024-2529 | unknown | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
| GO-2024-2530 | unknown | — | go.etcd.io/etcd | 0.5.0-alpha.5.0.20191023171146-3cf2f69b5738 | — |
Showing 30 of 30