Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-jhjp-4c2q-xmx4

k8saudit shipped rules do not detect privileged/sensitive settings on init or ephemeral containers

CVSS 4.3 Medium

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.

PackageEcosystemAffectedFixed in
github.com/falcosecurity/plugins/plugins/k8sauditGo<0.18.00.18.0
github.com/falcosecurity/plugins/plugins/k8saudit-eksGo<0.12.00.12.0
github.com/falcosecurity/plugins/plugins/k8saudit-gkeGo<0.9.00.9.0
github.com/falcosecurity/plugins/plugins/k8saudit-aksGo<0.6.00.6.0
github.com/falcosecurity/plugins/plugins/k8saudit-ovhGo<0.6.00.6.0
Identifiers
GHSA-jhjp-4c2q-xmx4 · GO-2026-6538
Weakness (CWE)
CWE-693
Tags
Published
21 Sept 2026
Updated
28 Sept 2026

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

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

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.