https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 17:14:09 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-26287 <p>External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. Starting in version 0.10.0 and prior to version 1.3.2, a bug in the `webhook` generator initialization order incorrectly cleared the label-enforcement flag (`EnforceLabels`) after it was set, resulting in the provider-side check for `external-secrets.io/type=webhook` being skipped (and the operation to succeed while it should have failed with `secret does not contain needed label &#39;external-secrets.io/type: webhook&#39;. Update secret label to use it with webhook`. Version 1.3.2 contains a patch.</p> <p>External Secrets Operator reads information from a third-party service and automatically injects the values as Kubernetes Secrets. Starting in version 0.10.0 and prior to version 1.3.2, a bug in the `webhook` generator initialization order incorrectly cleared the label-enforcement flag (`EnforceLabels`) after it was set, resulting in the provider-side check for `external-secrets.io/type=webhook` being skipped (and the operation to succeed while it should have failed with `secret does not contain needed label &#39;external-secrets.io/type: webhook&#39;. Update secret label to use it with webhook`. Version 1.3.2 contains a patch.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-26287 https://vulnerability.circl.lu/vuln/ghsa-q7hv-xx6h-q2x8 <p><strong>Affected:</strong> Go: github.com/external-secrets/external-secrets</p> <p>## Summary A bug in the `webhook` generator initialization order incorrectly cleared the label-enforcement flag (`EnforceLabels`) after it was set, resulting in the provider-side check for `external-secrets.io/type=webhook` being skipped (and the operation to succeed while it should have failed with `secret does not contain needed label &#39;external-secrets.io/type: webhook&#39;. Update secret label to use it with webhook`.</p> <p>## Impact A user with the permission to create webhook generator can set the webhook generator to a victim&#39; secret (which was not previously labelled for webhook&#39;s use), and exfiltrate it to a malicious URL.</p> <p>## Mitigations Until you upgrade, you can reduce risk by: - disabling webhook generators if not needed (or denying `generators.external-secrets.io/v1alpha1` `Webhook` via an admission policy); - restricting RBAC: limit who can create generators of kind `Webhook`; - enforcing an admission policy (OPA Gatekeeper / Kyverno) requiring referenced secrets to be labeled `external-secrets.io/type=webhook`; - restricting egress from external-secrets controller pods to an allowlist (kubernetes `NetworkPolicy` / service mesh egress policy).</p> <p>## References - PR #5901 (fix: webhook initialization order)</p> <p><strong>Affected:</strong> Go: github.com/external-secrets/external-secrets</p> <p>## Summary A bug in the `webhook` generator initialization order incorrectly cleared the label-enforcement flag (`EnforceLabels`) after it was set, resulting in the provider-side check for `external-secrets.io/type=webhook` being skipped (and the operation to succeed while it should have failed with `secret does not contain needed label &#39;external-secrets.io/type: webhook&#39;. Update secret label to use it with webhook`.</p> <p>## Impact A user with the permission to create webhook generator can set the webhook generator to a victim&#39; secret (which was not previously labelled for webhook&#39;s use), and exfiltrate it to a malicious URL.</p> <p>## Mitigations Until you upgrade, you can reduce risk by: - disabling webhook generators if not needed (or denying `generators.external-secrets.io/v1alpha1` `Webhook` via an admission policy); - restricting RBAC: limit who can create generators of kind `Webhook`; - enforcing an admission policy (OPA Gatekeeper / Kyverno) requiring referenced secrets to be labeled `external-secrets.io/type=webhook`; - restricting egress from external-secrets controller pods to an allowlist (kubernetes `NetworkPolicy` / service mesh egress policy).</p> <p>## References - PR #5901 (fix: webhook initialization order)</p> https://vulnerability.circl.lu/vuln/ghsa-q7hv-xx6h-q2x8