https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 23 Oct 2026 19:37:31 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-210102 EUVD-2026-210102 https://cve.radiocsirt.org/vuln/euvd-2026-210102 https://cve.radiocsirt.org/vuln/fkie_cve-2023-33191 <p>Kyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Users of the podSecurity `validate.podSecurity` subrule in Kyverno 1.9.2 and 1.9.3 are vulnerable. This issue was patched in version 1.9.4.</p> <p>Kyverno is a policy engine designed for Kubernetes. Kyverno seccomp control can be circumvented. Users of the podSecurity `validate.podSecurity` subrule in Kyverno 1.9.2 and 1.9.3 are vulnerable. This issue was patched in version 1.9.4.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-33191 https://cve.radiocsirt.org/vuln/ghsa-33hq-f2mf-jm3c <p><strong>Affected:</strong> Go: github.com/kyverno/kyverno</p> <p>### Impact</p> <p>Users of the podSecurity (`validate.podSecurity`) subrule in Kyverno versions v1.9.2 and v1.9.3 may be unable to enforce the check for the Seccomp control at the baseline level when using a `version` value of `latest`. There is no effect if a version number is referenced instead. See the [documentation](https://kyverno.io/docs/writing-policies/validate/#pod-security) for information on this subrule type. Users of Kyverno v1.9.2 and v1.9.3 are affected.</p> <p>### Patches</p> <p>v1.9.4 v1.10.0</p> <p>### Workarounds</p> <p>To work around this issue without upgrading to v1.9.4, temporarily install individual policies for the respective Seccomp checks in baseline [here](https://kyverno.io/policies/pod-security/baseline/restrict-seccomp/restrict-seccomp/) and restricted [here](https://kyverno.io/policies/pod-security/restricted/restrict-seccomp-strict/restrict-seccomp-strict/).</p> <p>### References</p> <p>* https://kyverno.io/docs/writing-policies/validate/#pod-security * https://github.com/kyverno/kyverno/pull/7263</p> <p><strong>Affected:</strong> Go: github.com/kyverno/kyverno</p> <p>### Impact</p> <p>Users of the podSecurity (`validate.podSecurity`) subrule in Kyverno versions v1.9.2 and v1.9.3 may be unable to enforce the check for the Seccomp control at the baseline level when using a `version` value of `latest`. There is no effect if a version number is referenced instead. See the [documentation](https://kyverno.io/docs/writing-policies/validate/#pod-security) for information on this subrule type. Users of Kyverno v1.9.2 and v1.9.3 are affected.</p> <p>### Patches</p> <p>v1.9.4 v1.10.0</p> <p>### Workarounds</p> <p>To work around this issue without upgrading to v1.9.4, temporarily install individual policies for the respective Seccomp checks in baseline [here](https://kyverno.io/policies/pod-security/baseline/restrict-seccomp/restrict-seccomp/) and restricted [here](https://kyverno.io/policies/pod-security/restricted/restrict-seccomp-strict/restrict-seccomp-strict/).</p> <p>### References</p> <p>* https://kyverno.io/docs/writing-policies/validate/#pod-security * https://github.com/kyverno/kyverno/pull/7263</p> https://cve.radiocsirt.org/vuln/ghsa-33hq-f2mf-jm3c https://cve.radiocsirt.org/vuln/gsd-2023-33191 gsd-2023-33191 https://cve.radiocsirt.org/vuln/gsd-2023-33191