CVE-2025-7445: Kubernetes secrets-store-sync-controller discloses service account tokens in logs
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:
bash 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 security@kubernetes.io
Acknowledgements
This vulnerability was reported by Reem Rotenberg and Kas Dekel from Microsoft.
Other sources
Kubernetes secrets-store-sync-controller in versions before 0.0.2 discloses service account tokens in logs.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-7445?
CVE-2025-7445 has been classified as a medium severity vulnerability due to the exposure of sensitive service account tokens in logs.
How do I fix CVE-2025-7445?
To mitigate CVE-2025-7445, update the Kubernetes secrets-store-sync-controller to version 0.0.2 or later.
What versions are affected by CVE-2025-7445?
CVE-2025-7445 affects all versions of Kubernetes secrets-store-sync-controller prior to 0.0.2.
What information is leaked by CVE-2025-7445?
CVE-2025-7445 discloses sensitive service account tokens in the logs, which could be exploited by an attacker.
Is there a workaround for CVE-2025-7445?
There is no official workaround for CVE-2025-7445; updating to a fixed version is the recommended action.