Security Deep Dive
milvus
Security posture and CVE patch evidence from tracked releases.
1 critical dependency CVE affects client/v2.6.5.
Audit transitive dependencies; consider upgrading or pinning replacements.
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.25 / 0.5
No EPSS data
freshness
1.00 / 1.0
3d stale
scorecard
1.56 / 4.0
Score 3.9/10
cve health
0.00 / 2.5
⚠ No direct scan — 4c/20h 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 56.2/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
0.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
4.4
10%
Provenance trust
provenance trust
3.9
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 56.2/100Scorecard
Scorecard 3.9/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 6 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 0 | dangerous workflow patterns detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| Security-Policy | 0 | security policy file not detected |
| CII-Best-Practices | 5 | badge detected: Passing |
| License | 10 | license file detected |
| Binary-Artifacts | 9 | binaries present in source code |
| Branch-Protection | 3 | branch protection is not maximal on development and all release branches |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Fuzzing | 0 | project is not fuzzed |
| Packaging | 10 | packaging workflow detected |
| SAST | 0 | SAST tool is not run on all commits -- score normalized to 0 |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
Dependency Vulnerabilities
Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.
Critical
1
High
3
Medium
4
Low
0
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2026-33186 | critical | — | google.golang.org/grpc | v1.71.1 | v2.6.16 |
| CVE-2026-24051 | high | — | go.opentelemetry.io/otel/sdk | v1.34.0 | v2.6.16 |
| CVE-2026-39883 | high | — | go.opentelemetry.io/otel/sdk | v1.34.0 | v2.6.16 |
| CVE-2026-41602 | high | — | github.com/apache/thrift | v0.20.0 | v2.6.16 |
| CVE-2022-29526 | medium | — | golang.org/x/sys | 0.0.0-20201223074533-0d417f636930 | v2.6.16 |
| CVE-2025-64702 | medium | — | github.com/quic-go/quic-go | v0.54.1 | v2.6.16 |
| GHSA-xmrv-pmrh-hhx2 | medium | — | github.com/aws/aws-sdk-go-v2/service/bedrockruntime | v1.23.0 | v2.6.16 |
| GHSA-xmrv-pmrh-hhx2 | medium | — | github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream | v1.6.7 | v2.6.16 |
| CVE-2026-33814 | unknown | — | golang.org/x/net | v0.52.0 | v2.6.16 |
Showing 9 of 53