Security Deep Dive
Kubo
Security posture and CVE patch evidence from tracked releases.
5 high-severity dependency CVEs affects v0.41.0.
Review the dependency vulnerabilities below.
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
6d stale
scorecard
2.44 / 4.0
Score 6.1/10
cve health
1.50 / 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.00 / 10.0
Risk 10.0/100
Score breakdown
schema v2Vulnerability posture
vulnerability posture
6.0
25%
Release responsiveness
release responsiveness
10.0
5%
Dependency exposure
dependency exposure
9.0
10%
Provenance trust
provenance trust
6.1
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 10.0/100Scorecard
Scorecard 6.1/10OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.
| Check | Score | Reason |
|---|---|---|
| Security-Policy | 10 | security policy file detected |
| Code-Review | 5 | Found 12/22 approved changesets -- score normalized to 5 |
| Maintained | 10 | 30 commit(s) and 23 issue activity found in the last 90 days -- score normalized to 10 |
| Dangerous-Workflow | 10 | no dangerous workflow patterns detected |
| Token-Permissions | 0 | detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0 | no effort to earn an OpenSSF best practices badge detected |
| Binary-Artifacts | 10 | no binaries found in the repo |
| Fuzzing | 0 | project is not fuzzed |
| License | 9 | license file detected |
| Branch-Protection | 8 | branch protection is not maximal on development and all release branches |
| Signed-Releases | 0 | Project has not signed or included provenance with any releases. |
| Packaging | 10 | packaging workflow detected |
| Pinned-Dependencies | 0 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | 10 | SAST tool detected |
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
0
High
5
Medium
7
Low
0
Unknown
1
| CVE | Severity | KEV | Dependency | Affected version | Cleared in release |
|---|---|---|---|---|---|
| CVE-2020-26279 | high | — | github.com/ipfs/go-ipfs | 0.7.0 | — |
| CVE-2022-23492 | high | — | github.com/libp2p/go-libp2p | 0.9.6 | — |
| CVE-2023-39533 | high | — | github.com/libp2p/go-libp2p | 0.9.6 | — |
| CVE-2023-40583 | high | — | github.com/libp2p/go-libp2p | 0.9.6 | — |
| CVE-2026-34986 | high | — | github.com/go-jose/go-jose/v4 | v4.1.3 | — |
| CVE-2020-26283 | medium | — | github.com/ipfs/go-ipfs | 0.7.0 | — |
| CVE-2023-22460 | medium | — | github.com/ipld/go-ipld-prime | 0.0.4-0.20200503082126-7e0619f3a984 | — |
| CVE-2023-23625 | medium | — | github.com/ipfs/go-unixfs | 0.2.4 | — |
| CVE-2026-35480 | medium | — | github.com/ipld/go-ipld-prime | 0.0.4-0.20200503082126-7e0619f3a984 | — |
| CVE-2026-39882 | medium | — | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp | v1.42.0 | — |
| CVE-2026-42328 | medium | — | github.com/ipld/go-ipld-prime | 0.0.4-0.20200503082126-7e0619f3a984 | — |
| GHSA-f2gr-7299-487h | medium | — | github.com/ipfs/go-ipfs | 0.7.0 | — |
| CVE-2023-26248 | unknown | — | github.com/libp2p/go-libp2p-kad-dht | v0.39.1 | — |
Showing 13 of 13