# CVE-2025-7445: Kubernetes secrets-store-sync-controller discloses service account tokens in logs

> Attackers with log access can steal service account tokens from Kubernetes secrets-store-sync-controller logs, compromising cluster security.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Sep 2025
- **Updated:** 5 Sep 2025
- **Also known as:** GHSA-rcw7-pqfp-735x, GO-2025-3939

## What is CVE-2025-7445?

CVE-2025-7445 is a medium-severity vulnerability in Kubernetes secrets-store-sync-controller, published on 5 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kubernetes secrets-store-sync-controller in versions before 0.0.2 discloses service account tokens in logs.

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

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

3 open source packages ship an affected version, including sigs.k8s.io/secrets-store-sync-controller.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sigs.k8s.io/secrets-store-sync-controller` | Go | All versions | 0.0.2 |
| `sigs.k8s.io/secrets-store-sync-controller` | Go | All versions | 0.0.2 |
| `sigs.k8s.io/secrets-store-sync-controller` | Go | All versions | 0.0.2 |

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

Upgrade sigs.k8s.io/secrets-store-sync-controller to 0.0.2 or later.

## Is CVE-2025-7445 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7445 is a medium-severity vulnerability in Kubernetes secrets-store-sync-controller, published on 5 Sep 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-7445 in the wild and no public exploit code.

Affected packages and fixed versions:
- sigs.k8s.io/secrets-store-sync-controller (Go): affected all versions; fixed in 0.0.2
- sigs.k8s.io/secrets-store-sync-controller (Go): affected all versions; fixed in 0.0.2
- sigs.k8s.io/secrets-store-sync-controller (Go): affected all versions; fixed in 0.0.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-7445/ (Markdown: https://insights.sbomify.com/CVE-2025-7445/index.md)
```

## Sources

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

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