critical

CVE

CVE-2026-122303, CVE-2026-122304, CVE-2026-122310, CVE-2026-122311, CVE-2026-122313, CVE-2026-122302, CVE-2026-122321, CVE-2026-122308, CVE-2026-122316, CVE-2026-122305, CVE-2026-122306, CVE-2026-122307, CVE-2026-122312, CVE-2026-122318, CVE-2026-122320, CVE-2026-122314, CVE-2026-122315, CVE-2026-122319, CVE-2026-122322, CVE-2026-122323, CVE-2026-103916, CVE-2026-122266, CVE-2026-122192

CWE

CWE-269, CWE-863, CWE-22, CWE-59, CWE-345, CWE-1188

Affected Surface

  • Kubernetes policy engine `kyverno` (`github.com/kyverno/kyverno`) versions `< 1.19.2` (`CVE-2026-122302` through `CVE-2026-122323` across 24 GitHub Security Advisories, including five CVSS 9.9 Critical and one CVSS 9.8 Critical cluster-admin escalations, fixed in `v1.19.2`)
  • Docker Sandboxes CLI (`sbx`) versions `< 0.51.0` (`CVE-2026-103916`, CVSS 8.2 High, incomplete fix in `0.48.0`, resolved in `v0.51.0`)
  • Amazon EKS Network Policy Agent (`github.com/aws/aws-network-policy-agent`) versions `< 1.3.7` bundled in Amazon VPC CNI (`github.com/aws/amazon-vpc-cni-k8s`) `< 1.22.3` (`CVE-2026-122266` / `GHSA-rp3x-m95q-87mx` / `GHSA-mm5f-ggvx-hmvw` / `AWS-2026-170`, CVSS 8.7 High)
  • AWS Firecracker microVM monitor (`github.com/firecracker-microvm/firecracker`) versions `0.23.0` through `1.16.1` (`CVE-2026-122192` / `GHSA-48ww-rqpp-2mgm` / `AWS-2026-169`, CVSS 7.5 High, fixed in `v1.16.2` and `v1.17.0`)

TL;DR

Between 3 and 5 November 2026, disclosures across Kubernetes admission controllers, AI-agent microVM sandboxes, eBPF CNI plugins, and cloud hypervisors exposed how multi-tenant confinement breaks when a privileged helper acts on paths or keys controlled by a tenant:

  1. Kyverno 1.19.2 patches 24 advisories (including five CVSS 9.9 Critical and one CVSS 9.8 Critical cluster-admin escalations, plus CVSS 9.1 verifyImages signature-cache bypass):
    • Unconfined CleanupPolicy context loader (CVE-2026-122304 / GHSA-p58h-r4j3-h5vx, CVSS 9.9 Critical): In pkg/controllers/cleanup/controller.go:174, the cleanup controller initialized its context loader with loader := ctxFactory(nil, kyvernov1.Rule{}). Because the first argument (policy) is what supplies policyNamespace to clamp spec.context apiCall URLs and block globalReference, passing nil set policyNamespace = "" and disabled all namespace confinement for every namespaced CleanupPolicy (a resource that Kyverno’s default Helm chart grants to every namespace admin via RBAC aggregation).
    • Query and fragment ../ smuggling in Policy.spec.context.apiCall.urlPath (CVE-2026-122310 / GHSA-3xfv-vq8x-qhg4, CVSS 9.9 Critical, incomplete fix for GHSA-5qq8-67g6-4h2w, plus CVE-2026-122312 / GHSA-pcx2-xcq4-65vf, CVSS 7.7): Kyverno 1.19.1 validated urlPath after running path.Clean, which treats ? and # as ordinary filename characters, and then handed the raw string to client-go, which strips query strings and fragments before resolving .. on the path. Hiding ../ after ? or # let a namespace tenant invoke arbitrary cluster-scoped Kubernetes API endpoints (MutatingWebhookConfiguration, ClusterRoleBinding, or cross-namespace Secret reads) using the admission controller’s ServiceAccount.
    • Path traversal in namespaced CEL resource.get() and resource.post() (CVE-2026-122311 / GHSA-4pqm-wqq6-h9q2, CVSS 9.9 Critical): In NamespacedValidatingPolicy, CEL calls to resource.get(apiVersion, resource, name) filled in the policy’s own namespace but did not reject .. or / segments in resource. Because client-go’s (*rest.Request).AbsPath joins segments with path.Join, passing .. walked out of /namespaces/<tenant>/ to read or write cluster-wide objects.
    • Cross-namespace resource overwrites via NamespacedMutatingPolicy mutateExisting (CVE-2026-122303 / GHSA-jcw5-3wcg-fqx5 and CVE-2026-122313 / GHSA-f96w-622v-rqpq, both CVSS 9.9 Critical; CVE-2026-122316 / GHSA-vm98-8c25-h274, CVSS 8.5): When evaluation.mutateExisting.enabled=true, pkg/background/mpol/processor.go evaluated targetMatchConstraints.expression and passed the returned objects straight to dclient.UpdateResource using Kyverno’s background-controller ServiceAccount without checking that the target’s namespace matched the policy’s namespace.
    • Controller-confused SubjectAccessReview in generate rules (CVE-2026-122302 / GHSA-q62c-r9v2-cf64, CVSS 9.8 Critical) and mutable tag caching in verifyImages (CVE-2026-122321 / GHSA-2r43-6962-xcw5, CVSS 9.1 Critical): Admission checks on generate rules verified the Kyverno controller’s permissions instead of the policy author’s (request.UserInfo), while verifyImages keyed its Ristretto verification cache on the raw imageRef string (such as a mutable :latest tag) rather than requiring an immutable digest (isDigestRef).
  2. Docker Sandboxes v0.51.0 (CVE-2026-103916, CVSS 8.2 High): Disclosed by Peyton Kennedy of Endor Labs on 3 November 2026, Docker’s microVM sandbox CLI (sbx) enforces a folder allowlist on its virtio-fs mount channel, but sbx cp performs host file I/O directly as the operator without consulting the allowlist. Its -L flag gated only one of the four symlink positions (copy-in source leaf), leaving copy-out destination leaf, copy-out destination parent, and copy-in source parent wide open to symlinks planted by an AI coding agent inside its workspace.
  3. Amazon EKS Network Policy Agent 1.3.7 / VPC CNI 1.22.3 (CVE-2026-122266 / AWS-2026-170, CVSS 8.7 High) and AWS Firecracker 1.16.2 / 1.17.0 (CVE-2026-122192 / AWS-2026-169, CVSS 7.5 High): In aws-network-policy-agent < 1.3.7, the eBPF conntrack map key omitted skb->ifindex, allowing a co-located pod sending crafted AF_PACKET frames to poison conntrack entries and bypass NetworkPolicy ingress rules on sibling pods (alongside an in-memory GetPodNamespacedName collision where ("ab", "c") and ("a", "bc") both hashed to "abc" and skipped TC probe attachment). In Firecracker 0.23.0 through 1.16.1, restoring a microVM from a snapshot with the File memory backend left unplugged virtio-mem or balloon regions writable by the VMM if a replacement mmap failed.

What to do now: Upgrade Kyverno to >= v1.19.2, upgrade Docker Sandboxes (sbx) to >= v0.51.0, upgrade the Amazon EKS VPC CNI add-on to >= v1.22.3 (aws-network-policy-agent >= v1.3.7; use v1.22.4 on SageMaker HyperPod), and upgrade AWS Firecracker to >= v1.16.2 or >= v1.17.0.

Affected packages and components

EcosystemProject / PackageCVE / AdvisorySeverityAffected versionsFixed versionVulnerable component
Go / Kuberneteskyverno (CleanupPolicy & APICall)CVE-2026-122304 (GHSA-p58h-r4j3-h5vx), CVE-2026-122310 (GHSA-3xfv-vq8x-qhg4), CVE-2026-122312 (GHSA-pcx2-xcq4-65vf)CVSS 9.9 Critical / 7.7 High1.17.0..1.19.1 (122304); 1.19.1 (122310, 122312)1.19.2pkg/controllers/cleanup/controller.go (ctxFactory(nil, ...)) and pkg/engine/apicall/apiCall.go
Go / Kuberneteskyverno (CEL resource.get/post & NamespacedMutatingPolicy)CVE-2026-122311 (GHSA-4pqm-wqq6-h9q2), CVE-2026-122303 (GHSA-jcw5-3wcg-fqx5), CVE-2026-122313 (GHSA-f96w-622v-rqpq), CVE-2026-122316 (GHSA-vm98-8c25-h274)CVSS 9.9 Critical / 8.5 High1.16.0..1.19.1 (122311); 1.17.0..1.19.1 (122303, 122313, 122316)1.19.2pkg/cel/libs/context.go, pkg/clients/dclient/path_segment.go, and pkg/background/mpol/processor.go
Go / Kuberneteskyverno (generate & verifyImages)CVE-2026-122302 (GHSA-q62c-r9v2-cf64), CVE-2026-122321 (GHSA-2r43-6962-xcw5), CVE-2026-122308 (GHSA-hg5v-hwm3-956r), CVE-2026-122320 (GHSA-493q-9xvg-9xf3)CVSS 9.8 & 9.1 Critical / 8.5 & 7.7 High< 1.19.2 (1.18.0..1.19.1 for 122321)1.19.2pkg/auth/auth.go, pkg/image/verification/cache/client.go, and pkg/background/generate/provenance
Go / CLIDocker Sandboxes (sbx)CVE-2026-103916CVSS 8.2 High< 0.51.0 (including incomplete fix in 0.48.0)0.51.0sbx cp host path resolution on copy-out destination and copy-in source parent components
Go / eBPF (EKS)aws-network-policy-agent / amazon-vpc-cni-k8sCVE-2026-122266 (GHSA-rp3x-m95q-87mx, GHSA-mm5f-ggvx-hmvw, AWS-2026-170)CVSS 8.7 Highaws-network-policy-agent < 1.3.7 (amazon-vpc-cni-k8s < 1.22.3)1.3.7 (VPC CNI 1.22.3 / 1.22.4)eBPF conntrack map key missing skb->ifindex (PR #584) and GetPodNamespacedName key collision (PR #563)
Rust / KVMAWS Firecracker (firecracker)CVE-2026-122192 (GHSA-48ww-rqpp-2mgm, AWS-2026-169)CVSS 7.5 High0.23.0 through 1.16.11.16.2, 1.17.0virtio-mem and balloon memory discard remap handling on snapshot restore (PR #6174)

Technical analysis

1. Kyverno 1.19.2: how ctxFactory(nil, ...), path.Join, and mutable tag caches broke multi-tenant isolation

Kyverno’s delegated multi-tenant model allows namespace admins to create namespaced policy resources (Policy, CleanupPolicy, NamespacedValidatingPolicy, NamespacedMutatingPolicy) while Kyverno’s admission and background controllers execute with cluster-wide ServiceAccounts. In v1.19.2, PRs #17984, #18021, #17994, and #17937 close five distinct paths where a namespace tenant could redirect those privileged ServiceAccounts across the cluster:

--- a/pkg/controllers/cleanup/controller.go
+++ b/pkg/controllers/cleanup/controller.go
@@ -171,7 +171,7 @@ func (c *controller) cleanup(ctx context.Context, logger logr.Logger, policy kyv
 	enginectx := enginecontext.NewContext(c.jp)
 	ctxFactory := factories.DefaultContextLoaderFactory(c.cmResolver, factories.WithGlobalContextStore(c.gctxStore))
-	loader := ctxFactory(nil, kyvernov1.Rule{})
+	loader := ctxFactory(policy, kyvernov1.Rule{})
--- a/pkg/image/verification/cache/client.go
+++ b/pkg/image/verification/cache/client.go
@@ -91,6 +91,15 @@ func generateKey(policy metav1.Object, ruleName string, imageRef string) string
+// isDigestRef reports whether imageRef is pinned to a digest (either
+// "repo@sha256:d" or "repo:tag@sha256:d"). Only such references are immutable
+// enough to key a verification verdict; a bare tag can be moved by the
+// registry after the entry is written.
+func isDigestRef(imageRef string) bool {
+	_, err := name.NewDigest(imageRef)
+	return err == nil
+}
  • The ctxFactory(nil, ...) one-liner (CVE-2026-122304): Because DefaultContextLoaderFactory originally accepted kyvernov1.PolicyInterface (which kyvernov2.CleanupPolicyInterface did not implement), the cleanup controller passed nil instead of policy. In DefaultContextLoaderFactory, if policy != nil && policy.IsNamespaced() evaluated to false, leaving policyNamespace = "" and turning every namespaced CleanupPolicy into an unconfined cluster-scoped context loader. PR #18021 introduces a minimal PolicyScope interface (metav1.Object + IsNamespaced() bool) implemented by both policy types and passes policy to ctxFactory.
  • Canonical URL and segment validation (CVE-2026-122310, CVE-2026-122311, CVE-2026-122312): PR #17984 adds canonicalizeURLPath() in pkg/engine/apicall/path.go, which parses urlPath with url.Parse, separates the path from any query or fragment, rejects .. and encoded separators, and matches the cleaned path against anchored regexes (^/api/[^/]+/namespaces/([^/]+)(?:/.*)?$) while explicitly excluding /api/v1/namespaces/<name> (namespaceObjectPathRegex, which is the cluster-scoped Namespace object itself). For CEL resource.Get/List/Post, pkg/clients/dclient/path_segment.go adds ValidatePathSegment() before any segment reaches (*rest.Request).AbsPath.
  • Digest-bound verifyImages caching (CVE-2026-122321) and HMAC-signed generate provenance (CVE-2026-122308): In pkg/image/verification/cache/client.go, Kyverno now refuses to cache verifyImages verdicts unless isDigestRef(imageRef) is true, and hashes the full resolved Attestor structs (attestorCacheRule in pkg/cel/libs/imageverify/impl.go) rather than just the attestor’s user-chosen label. For generate rules, PR #17937 provisions an installation-scoped HMAC-SHA256 signing secret (kyverno-generate-provenance) and records a signed generate.kyverno.io/provenance annotation so tenants cannot trigger synchronized generate rules simply by spoofing generate.kyverno.io/* labels on resources they create or update.

Docker Sandboxes runs AI coding agents (such as Claude Code, Codex, and Gemini CLI) inside a dedicated Linux microVM, sharing only explicitly approved host workspace directories into the guest via virtio-fs. However, when an operator copies build outputs, logs, or files between the host and the sandbox using sbx cp, the sbx CLI performs the host-side read or write directly in the host OS user’s context outside virtio-fs.

As Peyton Kennedy (Endor Labs) demonstrated, a prompt-injected agent inside the microVM can plant a dangling host symlink inside its writable workspace and wait for (or suggest) a routine sbx cp command:

# 1. Host-file WRITE escape (copy-out destination leaf or parent symlink):
# Inside the sandbox, the agent links ./results inside the workspace to ~/.ssh on the host:
ln -sfn /Users/$USER/.ssh /Users/$USER/project/work/results

# When the operator runs the documented copy-out command on the host:
sbx cp my-sandbox:/tmp/out/authorized_keys ~/project/work/results/
# -> sbx resolves ~/project/work/results/ on the host and overwrites ~/.ssh/authorized_keys!

# 2. Host-file READ escape (copy-in source parent symlink, without needing -L):
# Inside the sandbox, the agent links ./vendor to ~/.aws on the host:
ln -sfn /Users/$USER/.aws /Users/$USER/project/work/vendor

# When the operator copies a file from ./vendor into the sandbox (no -L flag passed):
sbx cp ~/project/work/vendor/credentials my-sandbox:/tmp/in/
# -> Because -L only checked the final path component ('credentials'), the parent symlink
#    'vendor' is followed on the host and ~/.aws/credentials is copied into the sandbox.

Docker Sandboxes v0.51.0 (released 3 November 2026 after an earlier v0.48.0 patch proved incomplete) confines the copy-out destination root and applies symlink checks across every path component of the copy-in source.

3. Amazon EKS Network Policy Agent 1.3.7 (CVE-2026-122266) and Firecracker 1.16.2 (CVE-2026-122192)

  • Cross-pod eBPF conntrack poisoning and GetPodNamespacedName collision in aws-network-policy-agent < 1.3.7 (CVE-2026-122266): On Amazon EKS nodes running the VPC CNI Network Policy Agent prior to v1.3.7 (VPC CNI < v1.22.3), the eBPF connection-tracking map key (20 bytes for IPv4, 56 bytes for IPv6) did not include the network interface index (skb->ifindex). A compromised pod with CAP_NET_RAW (AF_PACKET) could inject crafted frames that populated a conntrack entry matching a co-located victim pod’s 5-tuple, causing the victim pod’s eBPF ingress filter to treat subsequent unsolicited packets as established return traffic (PR #584 widens the key to 24 / 60 bytes by adding skb->ifindex and zero-initializing struct padding). In the same release, PR #563 fixes GetPodNamespacedName(), which previously concatenated name + namespace with no separator so pods ("ab", "c") and ("a", "bc") collided on "abc", causing isEBPFProbeAttached to skip installing the TC eBPF policy hook on the second pod.
  • Unmapped/writable VMM memory after failed remap in Firecracker < 1.16.2 (CVE-2026-122192): When a Firecracker microVM is restored from a snapshot backed by a File memory backend, discarding memory pages via virtio-mem (UNPLUG) or the virtio balloon device replaces the guest memory mapping. In Firecracker 0.23.0 through 1.16.1, if the host failed to create the replacement mapping during discard, the error handling left the underlying VMM memory slot in an inconsistent state accessible to guest root (PR #6174).

Detection and remediation

# 1. Check Kyverno deployment and image versions across Kubernetes clusters
kubectl get deploy -n kyverno -o jsonpath='{range .items[*]}{.metadata.name}: {.spec.template.spec.containers[*].image}{"\n"}{end}' 2>/dev/null || true

# 2. Audit existing namespaced Kyverno policies for apiCall, globalReference, resource.get/post, or mutateExisting
kubectl get policies,cleanuppolicies,namespacedvalidatingpolicies,namespacedmutatingpolicies -A -o yaml 2>/dev/null | \
  rg -n 'apiCall|globalReference|mutateExisting|resource\.(get|post|list)|cloneList' || true

# 3. Check Amazon EKS VPC CNI / Network Policy Agent, Docker sbx, and Firecracker versions
kubectl describe daemonset aws-node -n kube-system 2>/dev/null | rg 'amazon-k8s-cni|aws-network-policy-agent' || true
sbx --version 2>/dev/null || true
firecracker --version 2>/dev/null || true
  1. Upgrade Kyverno to >= v1.19.2: Audit all existing Policy, CleanupPolicy, NamespacedValidatingPolicy, and NamespacedMutatingPolicy resources in tenant namespaces for urlPath strings containing ?, #, %2e, or .., CEL resource.get/post calls with .., and resources carrying generate.kyverno.io/* labels without the new generate.kyverno.io/provenance annotation.
  2. Upgrade Docker Sandboxes (sbx) to >= v0.51.0: Until every developer machine is on v0.51.0, run realpath <host-path> before any sbx cp invocation to confirm that neither the leaf nor any parent directory resolves outside the workspace.
  3. Upgrade Amazon VPC CNI to >= v1.22.3 (v1.22.4 on SageMaker HyperPod) and Firecracker to >= v1.16.2 / v1.17.0: Note that upgrading aws-network-policy-agent to v1.3.7 automatically recreates the pinned eBPF conntrack map to accommodate the new 24-byte (IPv4) and 60-byte (IPv6) skb->ifindex keys, and Firecracker v1.16.2 bumps the snapshot format version (snapshots taken on 1.16.0 or 1.16.1 must be recreated).

Timeline

  • 2026-10-20 (23:50 UTC): Kyverno releases v1.19.2 containing PRs #17937, #17938, #17984, #17987, #17989, #17991, #17994, #17996, #18014, and #18021.
  • 2026-11-03: Docker releases Docker Sandboxes v0.51.0 to complete the fix for CVE-2026-103916; Endor Labs publishes its technical write-up.
  • 2026-11-04 (20:19 to 22:17 UTC): AWS publishes security bulletins 2026-169-AWS (CVE-2026-122192 for Firecracker 1.16.2 / 1.17.0) and 2026-170-AWS (CVE-2026-122266 for EKS Network Policy Agent 1.3.7 / VPC CNI 1.22.3).
  • 2026-11-05 (03:17 UTC): NVD and the GitHub Advisory Database publish 14 CVEs (CVE-2026-122302 through CVE-2026-122323) and 24 advisories for Kyverno 1.19.2.

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Use AI-native static analysis to find similar application vulnerabilities and generate review-ready fixes.

References