# k8saudit shipped rules do not detect privileged/sensitive settings on init or ephemeral containers Advisory record · `GHSA-jhjp-4c2q-xmx4` - **Identifiers:** `GHSA-jhjp-4c2q-xmx4` · `GO-2026-6538` - **State:** Confirmed - **Severity:** CVSS 4.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-693](https://cwe.mitre.org/data/definitions/693.html) - **Tags:** [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md) - **Published:** 21 Sept 2026 - **Updated:** 28 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 21 Sept 2026, 21:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/falcosecurity/plugins/plugins/k8saudit` (Go): affected `<0.18.0`; fixed in `0.18.0` - `github.com/falcosecurity/plugins/plugins/k8saudit-eks` (Go): affected `<0.12.0`; fixed in `0.12.0` - `github.com/falcosecurity/plugins/plugins/k8saudit-gke` (Go): affected `<0.9.0`; fixed in `0.9.0` - `github.com/falcosecurity/plugins/plugins/k8saudit-aks` (Go): affected `<0.6.0`; fixed in `0.6.0` - `github.com/falcosecurity/plugins/plugins/k8saudit-ovh` (Go): affected `<0.6.0`; fixed in `0.6.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The k8saudit plugin (versions below 0.18.0) and its cloud variants k8saudit-eks (below 0.12.0), k8saudit-gke (below 0.9.0), k8saudit-aks (below 0.6.0), and k8saudit-ovh (below 0.6.0) did not inspect security settings on initContainers or ephemeralContainers in pod specs. An actor who can create pods could run a privileged container by placing it in one of those lists, which evades the default Create Privileged Pod rule. Upgrade to k8saudit 0.18.0 or the matching cloud variant release (0.12.0, 0.9.0, 0.6.0, or 0.6.0), and review custom image allowlist rules. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** No score. ## Timeline - 31 Oct 2026, 14:12 UTC: First seen by agentprime - 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jhjp-4c2q-xmx4) ## Sources - [GitHub Advisory Database: GHSA-jhjp-4c2q-xmx4](https://github.com/advisories/GHSA-jhjp-4c2q-xmx4) - [OSV: GHSA-jhjp-4c2q-xmx4](https://osv.dev/vulnerability/GHSA-jhjp-4c2q-xmx4) - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .