Description
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 ignored in the API. SetUserGroups is alled on login, but instead of replacing the group memberships, they are appended. This may be due to some conflict with the group definitions in the config file, but that wasn't obvious to me if it were the case. Any Zot configuration that relies on group-based authorization will not respect group remove/revocation by an IdP. This issue has been addressed in version 2.1.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| project-zot | zot | < 2.1.2 | — |
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
SUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| SLES 15 SP6 | govulncheck-vulndb | 0.0.20250128T150132-150000.1.29.1 | SUSE-SU-2025:0297-1 |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | govulncheck-vulndb | 0.0.20250128T150132-1.1 | openSUSE-SU-2025:14710-1 |
| openSUSE Leap 15.6 | govulncheck-vulndb | 0.0.20250128T150132-150000.1.29.1 | SUSE-SU-2025:0297-1 |
Wolfi
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Wolfi rolling | zot | 2.1.2-r0 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| Go | zotregistry.dev/zot | < 2.1.2 | 2.1.2 | GHSA-c9p4-xwr9-rfhx |
| Go | zotregistry.dev/zot | all versions | — | GO-2025-3409 |
Advisories 2
- SUSE-SU-2025:0297-1 Security update for govulncheck-vulndb SUSE / openSUSE Security Updates · Feb 5, 2026
- openSUSE-SU-2025:14710-1 govulncheck-vulndb-0.0.20250128T150132-1.1 on GA media SUSE / openSUSE Security Updates · Feb 4, 2026