| Summary | External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. Prior to 2.4.0, Namespaced SecretStore resources that used CAProvider with type ConfigMap could resolve CA material from another namespace when caProvider.namespace was set. This bypassed the namespace boundary enforced for SecretStore-backed references in providers that rely on the shared runtime CA resolver. This vulnerability is fixed in 2.4.0. |
|---|---|
| Publication Date | May 12, 2026, 5:25 a.m. |
| Registration Date | May 13, 2026, 4:10 a.m. |
| Last Update | May 12, 2026, 5:25 a.m. |