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

Published Sep 5, 2025
·
Updated

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

2 affected componentsFixes available
Kubernetes secrets-store-sync-controller<0.0.2
go/sigs.k8s.io/secrets-store-sync-controller<0.0.2
0.0.2

Event History

Sep 5, 2025
CVE Published
via MITRE·02:31 AM
Data Sourced
via MITRE·02:31 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 AM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:02 PM
Data Sourced
via GitHub·09:02 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203