GHSA-jhjp-4c2q-xmx4: k8saudit shipped rules do not detect privileged/sensitive settings on init or ephemeral containers
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/falcosecurity/plugins/plugins/k8saudit (Go) 0.18.0; github.com/falcosecurity/plugins/plugins/k8saudit-aks (Go) 0.6.0; github.com/falcosecurity/plugins/plugins/k8saudit-eks (Go) 0.12.0.
Low priority for now. Upgrade to github.com/falcosecurity/plugins/plugins/k8saudit (Go) 0.18.0; github.com/falcosecurity/plugins/plugins/k8saudit-aks (Go) 0.6.0; github.com/falcosecurity/plugins/plugins/k8saudit-eks (Go) 0.12.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: OSV
The `k8saudit` plugin's per-container fields (`ka.req.pod.containers.*`) and the shipped `k8s_audit_rules.yaml` evaluated only `requestObject.spec.containers`. Security-relevant settings on a pod's `initContainers` or `ephemeralContainers` were not inspected, so the shipped `Create Privileged Pod` rule did not fire for a privileged container placed in either list. ### Impact An actor able to create pods (the activity k8saudit is intended to audit) could run a privileged container without triggering the default `Create Privileged Pod` rule, by declaring it as an `initContainer` or `ephemeralContainer` instead of a regular container. Kubernetes runs such containers with the requested privileges, but the shipped rule did not see them. The same gap applied to other per-container security settings (capabilities, `allowPrivilegeEscalation`, `runAsUser`, etc.) and, for deployments using a customized image allowlist, to disallowed images placed in those lists. This is a detection bypass of the default k8saudit ruleset, not a direct privilege escalation, and it requires the ability to create pods. The cloud-provider variants (`k8saudit-eks`, `k8saudit-gke`, `k8saudit-aks`, `k8saudit-ovh`) embed the same extraction logic and ship the same ruleset, and were affected equally. Note: adding an ephemeral container goes through the `pods/ephemeralcontainers` subresource, so the `EphemeralContainers Created` rule still logged that event at `NOTICE`, but without any privileged/security evaluation. ### Patches Fixed in `k8saudit 0.18.0`, and in the cloud-variant releases that depend on it — `k8saudit-eks 0.12.0`, `k8saudit-gke 0.9.0`, `k8saudit-aks 0.6.0`, `k8saudit-ovh 0.6.0` — all released on 2026-06-19. The fix ([falcosecurity/plugins#1400](https://github.com/falcosecurity/plugins/pull/1400), merged 2026-06-18) adds dedicated `ka.req.pod.initContainers.*` and `ka.req.pod.ephemeralContainers.*` field families and updates `Create Privileged Pod` (via a new `any_container_privileged` macro) to evaluate all three container lists. Operators upgrading should review any **custom** rules built on `ka.req.pod.containers.*` — in particular tuned `Create Disallowed Pod` image allowlists — and extend them to the new `initContainers`/`ephemeralContainers` image fields. ### Workarounds For deployments that cannot upgrade immediately, restrict who can create pods (RBAC) and enforce Pod Security Admission (`baseline`/`restricted`) or an admission controller (Kyverno, OPA/Gatekeeper) to block privileged init/ephemeral containers at admission time, as defense-in-depth. ### Credits [kanywst](https://github.com/kanywst) — discovery and fix.
- Published
- Sep 21, 2026
- Updated
- Sep 28, 2026
- EPSS
- —
- CWE
- CWE-693
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| Go | github.com/falcosecurity/plugins/plugins/k8saudit | pkg:golang/github.com/falcosecurity/plugins/plugins/k8saudit |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-eks | pkg:golang/github.com/falcosecurity/plugins/plugins/k8saudit-eks |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-gke | pkg:golang/github.com/falcosecurity/plugins/plugins/k8saudit-gke |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-aks | pkg:golang/github.com/falcosecurity/plugins/plugins/k8saudit-aks |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-ovh | pkg:golang/github.com/falcosecurity/plugins/plugins/k8saudit-ovh |
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/falcosecurity/plugins/plugins/k8saudit | before 0.18.0 | 0.18.0 |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-aks | before 0.6.0 | 0.6.0 |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-eks | before 0.12.0 | 0.12.0 |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-gke | before 0.9.0 | 0.9.0 |
| Go | github.com/falcosecurity/plugins/plugins/k8saudit-ovh | before 0.6.0 | 0.6.0 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/falcosecurity/plugins/plugins/k8saudit | 0.18.0 | Package registry (OSV) |
| Go:github.com/falcosecurity/plugins/plugins/k8saudit-aks | 0.6.0 | Package registry (OSV) |
| Go:github.com/falcosecurity/plugins/plugins/k8saudit-eks | 0.12.0 | Package registry (OSV) |
| Go:github.com/falcosecurity/plugins/plugins/k8saudit-gke | 0.9.0 | Package registry (OSV) |
| Go:github.com/falcosecurity/plugins/plugins/k8saudit-ovh | 0.6.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-693 · Protection Mechanism FailureCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
osv
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Site TracingCAPEC-107likelihood: Medium · Very High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Escaping a Sandbox by Calling Code in Another LanguageCAPEC-237likelihood: Low · Very High
- Using Unpublished Interfaces or FunctionalityCAPEC-36likelihood: Medium · High
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- github.com/falcosecurity/plugins/pull/1400
- github.com/falcosecurity/plugins/commit/0adb9b3c7e2c8bad53f30d01c057e038b2afa5e1
- github.com/falcosecurity/plugins
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-aks/v0.6.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-eks/v0.12.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-gke/v0.9.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit-ovh/v0.6.0
- github.com/falcosecurity/plugins/releases/tag/plugins/k8saudit/v0.18.0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.