PT-2025-36631 · Go · Sigs.K8S.Io/Secrets-Store-Sync-Controller

Published 2025-09-05 · Updated 2025-09-05

OSV

CVSS v3.1

6.5

Medium

Base vector

AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Hello Kubernetes Community,

A security issue was discovered in secrets-store-sync-controller where an actor with access to the controller logs could observe service account tokens. These tokens could then potentially be exchanged with external cloud providers to access secrets stored in cloud vault solutions. Tokens are only logged when there is a specific error marshaling the parameters sent to the providers.

Am I vulnerable?

To check if tokens are being logged, examine the manager container log:

kubectl logs -l 'app.kubernetes.io/part-of=secrets-store-sync-controller' -c manager -f | grep --line-buffered "csi.storage.k8s.io/serviceAccount.tokens"

Affected Versions

• secrets-store-sync-controller < v0.0.2

How do I mitigate this vulnerability?

Upgrade to secrets-store-sync-controller v0.0.2+

Fixed Versions

• secrets-store-sync-controller >= v0.0.2

Detection

Examine cloud provider logs for unexpected token exchanges, as well as unexpected access to cloud vault secrets.

If you find evidence that this vulnerability has been exploited, please contact [e-mail]

Acknowledgements

This vulnerability was reported by Reem Rotenberg and Kas Dekel from Microsoft.

Fix

Insertion into Log File

Weakness Enumeration

CWE-532

Related Identifiers

GHSA-RCW7-PQFP-735X

Affected Products

Sigs.K8S.Io/Secrets-Store-Sync-Controller

References · 6

• https://nvd.nist.gov/vuln/detail/CVE-2025-7445 · Security Note
• https://osv.dev/vulnerability/GHSA-rcw7-pqfp-735x · Vendor Advisory
• https://github.com/kubernetes/kubernetes/issues/133897 · Note
• https://github.com/kubernetes-sigs/secrets-store-sync-controller/security/advisories/GHSA-rcw7-pqfp-735x · Note
• https://github.com/kubernetes-sigs/secrets-store-sync-controller · Note
• https://groups.google.com/g/kubernetes-security-announce/c/NP7cQvQ1aGA · Note