Access Control Bypass Affecting github.com/external-secrets/external-secrets/pkg/controllers/pushsecret package, versions >=0.15.0 <0.19.2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Access Control Bypass vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOMEXTERNALSECRETSEXTERNALSECRETSPKGCONTROLLERSPUSHSECRET-11799544
- published14 Aug 2025
- disclosed13 Aug 2025
- creditMoritz Johner
Introduced: 13 Aug 2025
NewCVE-2025-55196 (opens in a new tab)How to fix?
Upgrade github.com/external-secrets/external-secrets/pkg/controllers/pushsecret to version 0.19.2 or higher.
Overview
Affected versions of this package are vulnerable to Access Control Bypass via the List() calls for Kubernetes Secret and SecretStore resources performed by the PushSecret controller, which does not apply a namespace selector. An attacker can access sensitive information from arbitrary namespaces by leveraging label selectors to list and read secrets or secret-stores across the cluster.
Note:
This is exploitable if the attacker has permissions to create or update PushSecret resources and control one or more SecretStore resources.
Workaround
This vulnerability can be mitigated by restricting RBAC permissions so that only trusted service accounts can create or update PushSecret and SecretStore resources, auditing existing resources to ensure they are controlled by trusted parties, and reviewing Network Policies to prevent data exfiltration.