# CVE-2025-48374: zot logs secrets

> Attackers with log access can steal Keycloak client secrets exposed in zot container startup logs when using OIDC authentication.

- **Severity:** Medium 5.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-c37v-3c8w-crq8, GO-2025-3705

## What is CVE-2025-48374?

CVE-2025-48374 is a medium-severity vulnerability in project-zot zot, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. Prior to version 2.1.3 (corresponding to pseudoversion 1.4.4-0.20250522160828-8a99a3ed231f), when using Keycloak as an oidc provider, the clientsecret gets printed into the container stdout logs for an example at container startup. Version 2.1.3 (corresponding to pseudoversion 1.4.4-0.20250522160828-8a99a3ed231f) fixes the issue.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-48374?

3 open source packages ship an affected version, including zotregistry.dev/zot.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zotregistry.dev/zot` | Go | All versions | 1.4.4-0.20250522160828-8a99a3ed231f |
| `zotregistry.dev/zot` | Go | All versions | 1.4.4-0.20250522160828-8a99a3ed231f |
| `zotregistry.dev/zot` | Go | All versions | 1.4.4-0.20250522160828-8a99a3ed231f |

## How do I fix CVE-2025-48374?

Upgrade zotregistry.dev/zot to 1.4.4-0.20250522160828-8a99a3ed231f or later.

## Is CVE-2025-48374 being exploited?

There is no known exploitation of CVE-2025-48374 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48374 and fix it if it is affected.

What it is: CVE-2025-48374 is a medium-severity vulnerability in project-zot zot, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48374 in the wild and no public exploit code.

Affected packages and fixed versions:
- zotregistry.dev/zot (Go): affected all versions; fixed in 1.4.4-0.20250522160828-8a99a3ed231f
- zotregistry.dev/zot (Go): affected all versions; fixed in 1.4.4-0.20250522160828-8a99a3ed231f
- zotregistry.dev/zot (Go): affected all versions; fixed in 1.4.4-0.20250522160828-8a99a3ed231f

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-48374/ (Markdown: https://insights.sbomify.com/CVE-2025-48374/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48374
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48374
- OSV: https://osv.dev/vulnerability/CVE-2025-48374

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48374/
Summaries are generated and may contain mistakes; the official description above is the record.