# CVE-2025-23208: IdP group membership revocation ignored in zot > Attackers retain revoked group access in zot registry due to append-only group storage, bypassing authorization controls. - **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 Jan 2025 - **Updated:** 22 Jan 2025 - **Also known as:** GHSA-c9p4-xwr9-rfhx, GO-2025-3409 ## What is CVE-2025-23208? CVE-2025-23208 is a high-severity missing authorization vulnerability in project-zot zot, published on 17 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-269 (Improper Privilege Management) ## Which versions are affected by CVE-2025-23208? 3 open source packages ship an affected version, including zotregistry.dev/zot. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `zotregistry.dev/zot` | Go | All versions | None | | `zotregistry.dev/zot` | Go | All versions | 2.1.2 | | `zotregistry.dev/zot` | Go | All versions | 2.1.2 | Products: Zotregistry Zot. ## How do I fix CVE-2025-23208? Upgrade zotregistry.dev/zot to 2.1.2 or later. ## Is CVE-2025-23208 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23208 exists. ## Other vulnerabilities in project-zot zot - [CVE-2026-31801](https://insights.sbomify.com/CVE-2026-31801/): zot create-only policy allows overwrite attempts of existing latest tag (update permission not required) (high 7.7) - [CVE-2024-39897](https://insights.sbomify.com/CVE-2024-39897/): Cache driver GetBlob() allows read access to any blob without access control check (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-23208 and fix it if it is affected. What it is: CVE-2025-23208 is a high-severity missing authorization vulnerability in project-zot zot, published on 17 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-23208 exists. Affected packages and fixed versions: - zotregistry.dev/zot (Go): affected all versions; no fix listed - zotregistry.dev/zot (Go): affected all versions; fixed in 2.1.2 - zotregistry.dev/zot (Go): affected all versions; fixed in 2.1.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-23208/ (Markdown: https://insights.sbomify.com/CVE-2025-23208/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-23208 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-23208 - OSV: https://osv.dev/vulnerability/CVE-2025-23208 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-23208/ Summaries are generated and may contain mistakes; the official description above is the record.