Zotregistry maintains Zot, a container registry implementation, with a focused vulnerability profile centered on authorization and access-control mechanisms. The recurring weakness classes, including authorization bypass through user-controlled keys, improper privilege management, and incorrect authorization, reflect the authentication and role-enforcement demands of a privileged artifact-storage component; current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Zotregistry over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-31801HIGH zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. From 1.3.0 to 2.1.14, zot’s dist-spec authorization middleware infers | Mar 10, 2026 | 7.7 | 24 | NO | NO |
CVE-2025-23208MEDIUM zot is a production-ready vendor-neutral OCI image registry. The group data stored for users in the boltdb database (meta.db) is an append-list so group revocations/removals are ig | Jan 17, 2025 | 5.3 | 17 | NO | NO |
CVE-2024-39897MEDIUM zot is an OCI image registry. Prior to 2.1.0, the cache driver `GetBlob()` allows read access to any blob without access control check. If a Zot `accessControl` policy allows users | Jul 9, 2024 | 4.3 | 15 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Zotregistry.
Media articles that mention a CVE ID that affects a product developed by Zotregistry — matched by CVE ID, not by vendor name.