Zot IdP group membership revocation ignored

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2025-23208: 0.42% estimated exploitation activity in the next 30 days; percentile 36.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details 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. PoC Login with group claims, logout, remove the user from a group from at IdP and log in again, the API still grants access and the new list of groups is appended creating meaningless duplicate entries and no longer mathing the expected groups from the IdP. The behavior can be verified by seeing the API or UI still presenting images it should not or by viewing the data directly: bbolt get meta.db UserData <user, eg: Note this example also has duplicates due to group hierarchy changes that were left in the database. Impact Any Zot configuration that relies on group-based authorization will not respect group…

Published by the source

17 Jan 2025, 22:02 UTC

Last modified by the source

21 Jan 2025, 18:31 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c9p4-xwr9-rfhx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-23208

Advisory: Zot IdP group membership revocation ignored
IDs: CVE-2025-23208, GHSA-c9p4-xwr9-rfhx
Record: https://patchnext.com/advisories/cve-2025-23208 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zotregistry.dev/zot 2.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go zotregistry.dev/zot: affected <= 2.1.1; fixed in 2.1.2

## Suggested inspection (read-only)
- Go zotregistry.dev/zot: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zotregistry.dev/zot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c9p4-xwr9-rfhx (GitHub-reviewed advisory GHSA-c9p4-xwr9-rfhx lists affected ranges: Go zotregistry.dev/zot >=0 <=2.1.1)

Commands are suggestions: review each one before running it.