Security Deep Dive
vitess
Security posture and CVE patch evidence from tracked releases.
1 critical dependency CVE affects v24.0.2.
Audit transitive dependencies; consider upgrading or pinning replacements.
Trust Signals — 3 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
1d stale
scorecard
3.12 / 4.0
Score 7.8/10
cve health
1.00 / 2.5
No open 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 46.7/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
4.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
5.3
10%
Provenance trust
provenance trust
7.8
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 46.7/100Scorecard
Scorecard 7.8/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Code-Review | 10 | all changesets reviewed |
| Maintained | 10 | 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |
| Dependency-Update-Tool | 10 | update tool detected |
| Security-Policy | 10 | security policy file detected |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| CII-Best-Practices | 5 | badge detected: Passing |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 9 | binaries present in source code |
| Pinned-Dependencies | 9 | dependency not pinned by hash detected -- score normalized to 9 |
| SAST | 7 | SAST tool detected but not run on all commits |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Packaging | 10 | packaging workflow detected |
| License | 10 | license file detected |
| Branch-Protection | 8 | branch protection is not maximal on development and all release branches |
| Fuzzing | 10 | project is fuzzed |
| Vulnerabilities | 7 | 3 existing vulnerabilities detected |
| CI-Tests | 10 | 30 out of 30 merged PRs checked by a CI test -- score normalized to 10 |
| Contributors | 10 | project has 19 contributing companies or organizations |
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
1
High
21
Medium
14
Low
1
Unknown
0
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2015-7501 | critical | — | org.apache.commons:commons-collections4 | — | v23.0.4 |
| CVE-2015-6420 | high | — | org.apache.commons:commons-collections4 | — | v23.0.4 |
| CVE-2016-4970 | high | — | io.netty:netty-handler | — | v23.0.4 |
| CVE-2020-11612 | high | — | io.netty:netty-handler | — | v23.0.4 |
| CVE-2020-7238 | high | — | io.netty:netty-handler | — | v23.0.4 |
| CVE-2021-22569 | high | — | com.google.protobuf:protobuf-java | — | v23.0.4 |
| CVE-2022-21698 | high | — | github.com/prometheus/client_golang | 1.6.0 | v23.0.4 |
| CVE-2022-25647 | high | — | com.google.code.gson:gson | — | v23.0.4 |
| CVE-2022-3509 | high | — | com.google.protobuf:protobuf-java | — | v23.0.4 |
| CVE-2022-3510 | high | — | com.google.protobuf:protobuf-java | — | v23.0.4 |
| CVE-2023-1428 | high | — | io.grpc:grpc-protobuf | — | v23.0.4 |
| CVE-2023-32731 | high | — | io.grpc:grpc-protobuf | — | v23.0.4 |
| CVE-2024-47554 | high | — | commons-io:commons-io | — | v23.0.4 |
| CVE-2024-7254 | high | — | com.google.protobuf:protobuf-java | — | v23.0.4 |
| CVE-2025-24970 | high | — | io.netty:netty-handler | — | v23.0.4 |
| CVE-2025-65637 | high | — | github.com/sirupsen/logrus | 1.6.0 | v23.0.4 |
| CVE-2026-26996 | high | — | minimatch | 5.1.6 | v23.0.4 |
| CVE-2026-27601 | high | — | underscore | 1.13.7 | v23.0.4 |
| CVE-2026-27903 | high | — | minimatch | 5.1.6 | v23.0.4 |
| CVE-2026-27904 | high | — | minimatch | 5.1.6 | v23.0.4 |
| CVE-2026-6321 | high | — | fast-uri | 3.0.6 | v23.0.4 |
| CVE-2026-6322 | high | — | fast-uri | 3.0.6 | v23.0.4 |
| CVE-2014-3488 | medium | — | io.netty:netty-handler | — | v23.0.4 |
| CVE-2018-10237 | medium | — | com.google.guava:guava | — | v23.0.4 |
| CVE-2019-11254 | medium | — | gopkg.in/yaml.v2 | 2.2.5 | v23.0.4 |
| CVE-2019-20445 | medium | — | io.netty:netty-handler | — | v23.0.4 |
| CVE-2020-15250 | medium | — | junit:junit | — | v23.0.4 |
| CVE-2021-29425 | medium | — | commons-io:commons-io | — | v23.0.4 |
| CVE-2022-29526 | medium | — | golang.org/x/sys | 0.0.0-20200519105757-fe76b779f299 | v23.0.4 |
| CVE-2022-3171 | medium | — | com.google.protobuf:protobuf-java | — | v23.0.4 |
| CVE-2023-2976 | medium | — | com.google.guava:guava | — | v23.0.4 |
| CVE-2023-32732 | medium | — | io.grpc:grpc-protobuf | — | v23.0.4 |
| CVE-2023-34462 | medium | — | io.netty:netty-handler | — | v23.0.4 |
| CVE-2025-69873 | medium | — | ajv | 8.17.1 | v23.0.4 |
| CVE-2026-2327 | medium | — | markdown-it | 14.1.0 | v23.0.4 |
| CVE-2026-33750 | medium | — | brace-expansion | 2.0.2 | v23.0.4 |
| CVE-2020-8908 | low | — | com.google.guava:guava | — | v23.0.4 |
Showing 37 of 37