Tools / zot / Security

Security Deep Dive

zot

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 actively-exploited dependency CVE affects v2.1.17.

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.

4 versions tracked

Version	Published	C	H	M	L	KEV	Notes
v2.1.17	2026-05-18	—	—	—	—	—	Latest Patches CVE-2026-33634
v2.1.16	2026-04-19	—	1	—	—	KEV 1	—
v2.1.15	2026-03-08	—	1	—	—	KEV 1	Patches GHSA-85jx-fm8m-x8c6 Patches GO-2026-4668
v2.1.14	2026-01-25	—	2	—	—	KEV 1	—

— Signed — SLSA — SBOM ✓ Security policy Monthly cadence · 41d median Active maintainer

Trust Signals — 3 of 9 Present

Evidence already collected from releases and repository metadata.

3/9 Present

Signed releases Unknown

Latest release artifact signature Latest release

—

SLSA provenance Unknown

Attestation predicate level Latest release

—

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Present

GitHub repository metadata Repository policy

Checked: 23d ago

Release cadence: monthly Present

41d median over recent releases Release history

Latest release: 16d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 3d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 16d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 16d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 16d ago

2.2/10 Security Score

8.1/10 Scorecard

0d avg CVE Patch Speed

Open CVEs Open CVEs detected for latest version.

Patch speed: 0d

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.50 / 0.5

Max EPSS 0.294

freshness

1.00 / 1.0

3d stale

scorecard

3.24 / 4.0

Score 8.1/10

cve health

0.00 / 2.5

Open CVEs detected

patch speed

0.50 / 0.5

0d avg

kev exposure

-1.50 / 1.5

KEV exposure detected

supply chain risk

-1.50 / 10.0

Risk 15.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: 0

Dependency exposure

dependency exposure

8.5

10%

supply chain risk: 15.0 transitive cves: 0c/0h

Provenance trust

provenance trust

8.1

40%

scorecard score: 8.1 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 3d

Operational risk

operational risk

3.0

10%

kev exposure: detected epss max: 0.294

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 15.0/100

0 Transitive critical CVEs

1 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 8.1/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Maintained	10	30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Security-Policy	10	security policy file detected
Dependency-Update-Tool	10	update tool detected
Code-Review	9	Found 27/30 approved changesets -- score normalized to 9
Dangerous-Workflow	10	no dangerous workflow patterns detected
Binary-Artifacts	10	no binaries found in the repo
Token-Permissions	10	GitHub workflow tokens follow principle of least privilege
CII-Best-Practices	5	badge detected: Passing
Packaging	10	packaging workflow detected
Vulnerabilities	0	24 existing vulnerabilities detected
Pinned-Dependencies	7	dependency not pinned by hash detected -- score normalized to 7
Fuzzing	10	project is fuzzed
Signed-Releases	0	Project has not signed or included provenance with any releases.
License	10	license file detected
SAST	10	SAST tool is run on all commits
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
CI-Tests	10	30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Contributors	10	project has 21 contributing companies or organizations

CVE Patch History

Median patch time: 0 days

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

Critical High Medium Low

2026

CVE	Severity	EPSS	Disclosed	Fixed in	Days to fix	vs Ecosystem Median	KEV
CVE-2026-33634	HIGH	96%ile	—	v2.1.17	—	—	KEV
GHSA-85jx-fm8m-x8c6	High	—	—	v2.1.15	—	—	—
GO-2026-4668	unknown	—	—	v2.1.15	—	—	—

KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.

Dependency Vulnerabilities

588 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

1 dependency vulnerabilities are in KEV.

CISA confirmed these vulnerabilities are actively exploited. Treat as critical priority.

Still affecting latest (3) All (5)

Medium 1 Unknown 4

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2026-41888	medium	—	github.com/distribution/distribution/v3	v3.1.0	v2.1.17
CVE-2020-8911	unknown	—	github.com/aws/aws-sdk-go	v1.55.8	v2.1.17
CVE-2020-8912	unknown	—	github.com/aws/aws-sdk-go	v1.55.8	v2.1.17
CVE-2026-24122	unknown	—	github.com/sigstore/cosign/v2	v2.6.2	v2.1.17
CVE-2026-33634	unknown	KEV	github.com/aquasecurity/trivy	v0.70.0	—

Showing 5 of 5