Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

sigs.k8s.io/secrets-store-sync-controller

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5GoPublished

    secrets-store-sync-controller discloses service account tokens in logs

    CVE-2025-7445 · GHSA-rcw7-pqfp-735x

    Affected
    • Go sigs.k8s.io/secrets-store-sync-controller < 0.0.2
    Fixed in
    0.0.2· Vendor fix available
    Issue
    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: 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…

    Recommended action: Upgrade to 0.0.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →