github.com/falcosecurity/plugins/plugins/k8saudit · k8saudit shipped rules do not detect privileged/sensitive settings on init or ephemeral containers
Affects github.com/falcosecurity/plugins/plugins/k8sauditSource GCVE Database
CVSS 4.3 Medium : upgrade to 0.18.0 when convenient.
Data as of 24 Sep 2026, 04:34 UTC
- Patch
- Available – fixed in 0.18.0, 0.12.0, 0.9.0 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NWhat to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/falcosecurity/plugins/plugins/k8saudit | Affected
| Fixed in
|
| Gogithub.com/falcosecurity/plugins/plugins/k8saudit-eks | Affected
| Fixed in
|
| Gogithub.com/falcosecurity/plugins/plugins/k8saudit-gke | Affected
| Fixed in
|
| Gogithub.com/falcosecurity/plugins/plugins/k8saudit-aks | Affected
| Fixed in
|
| Gogithub.com/falcosecurity/plugins/plugins/k8saudit-ovh | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in k8saudit 0.18.0 and cloud-provider variants released on 2026-06-19. Operators should upgrade to these versions to ensure auditing covers initContainers and ephemeralContainers. Until upgrades can be applied, restrict pod creation permissions via RBAC and enforce Pod Security Admission policies (baseline or restricted) or admission controllers such as Kyverno or OPA/Gatekeeper to block privileged init or ephemeral containers at admission time as defense-in-depth. Operators with custom rules referencing ka.req.pod.containers.* should update them to include the new initContainers and ephemeralContainers fields.
Description
The k8saudit plugin's default rules did not inspect security-relevant settings on Kubernetes initContainers and ephemeralContainers, only regular containers. This allowed pod creators to run privileged or otherwise sensitive containers in these container types without triggering the default 'Create Privileged Pod' detection rule. The issue affects k8saudit and its cloud-provider variants. A fix was released in k8saudit 0.18.0 and corresponding cloud variants on 2026-06-19. Until upgraded, restricting pod creation and enforcing Pod Security Admission or admission controllers can mitigate risk.
References
- github.com/falcosecurity/plugins/security/advisories/GHSA-jhjp-4c2q-xmx4 (opens in a new tab)
- github.com/falcosecurity/plugins/pull/1400 (opens in a new tab)
- github.com/falcosecurity/plugins/commit/0adb9b3c7e2c8bad53f30d01c057e038b2afa5e1 (opens in a new tab)
- github.com/falcosecurity/plugins (opens in a new tab)
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-aks/v0.6.0 (opens in a new tab)
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-eks/v0.12.0 (opens in a new tab)
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-gke/v0.9.0 (opens in a new tab)
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-ovh/v0.6.0 (opens in a new tab)
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit/v0.18.0 (opens in a new tab)