Skip to content
Edition of Thursday, November 19, 2026
Daily CISO

The five-minute briefing for security leaders.

Guide

Kubernetes Security News: 2026's CVEs, the Ingress NGINX Retirement and the Trivy Compromise

Every 2026 Kubernetes security advisory from the project's CVE feed, the ingress-nginx flaw left unfixed, supported versions, and the exploited Trivy compromise.

Published November 15, 2026Updated Daily CISO Desk7 sources

The Kubernetes project has published 13 security advisories in 2026, and 8 of them are in ingress-nginx, the popular traffic controller the project retired in March. The newest, CVE-2026-116472 (November 5), will never get an upstream fix. No Kubernetes component appears in CISA's catalog of actively exploited flaws, but the Trivy scanner many clusters use does: its March 2026 supply-chain compromise is listed as exploited.

The counts on this page are this site's own. We read every entry in the project's official CVE feed and every entry in CISA's Known Exploited Vulnerabilities (KEV) catalog. The methods note at the end sets out the rules.

Key facts

  • 95 advisories in the Kubernetes official CVE feed, from March 21, 2017 to November 5, 2026. 15 were published in 2025 and 13 so far in 2026.
  • 20 of the 95 are in ingress-nginx, more than any other component. Eight of those 20 arrived in 2026.
  • March 2026: ingress-nginx maintenance ended. Kubernetes says it will not fix CVE-2026-116472.
  • 1.37, 1.36 and 1.35 are the supported Kubernetes minor releases. Version 1.34 reached end of life on October 27, 2026.
  • 0 Kubernetes project CVEs in CISA's KEV catalog (version 2026.11.13, 1,781 entries). 1 entry for the Trivy scanner, added March 26, 2026.

Which Kubernetes vulnerabilities were disclosed in 2026?

The project's feed lists 13 advisories published between February 2 and November 5, 2026. The scores below are the CVSS 3.1 base scores each advisory states; five advisories give only the vector.

PublishedCVEComponentWhat it allowsCVSS
Nov 5CVE-2026-116472ingress-nginxDenial of service of the data plane through the mirror-target annotation; no upstream fix2.7
Sep 14CVE-2026-76654kubelet (Windows nodes)NTLM hash theft through a subPath symlink to a network share5.8
Sep 14CVE-2026-2270kube-controller-managerCross-namespace pod creation through StatefulSet and ControllerRevision writes5.9
Aug 10CVE-2026-19444kubectl (Windows)Arbitrary file writes on the user's machine during kubectl cp6.5
Apr 10CVE-2026-3865CSI Driver for SMBPath traversal in subDir that may delete directories on the SMB server6.5
Mar 19CVE-2026-4342ingress-nginxnginx configuration injection through comment-based annotations8.8
Mar 17CVE-2026-3864CSI Driver for NFSPath traversal in subDir that may delete directories on the NFS server6.5
Mar 9CVE-2026-3288ingress-nginxnginx configuration injection through the rewrite-target annotation8.8
Feb 6CVE-2025-15566ingress-nginxnginx configuration injection through auth-proxy-set-headersvector only
Feb 2CVE-2026-24514ingress-nginxDenial of service of the admission controllervector only
Feb 2CVE-2026-24513ingress-nginxBypass of auth-url protectionvector only
Feb 2CVE-2026-24512ingress-nginxnginx configuration injection through rules.http.paths.pathvector only
Feb 2CVE-2026-1580ingress-nginxnginx configuration injection through the auth-method annotationvector only

Five of the eight ingress-nginx advisories describe the same outcome: arbitrary code execution in the controller and disclosure of the Secrets it can read. The advisories add that in a default installation the controller can read every Secret in the cluster, so one malicious Ingress object can expose credentials far outside its own namespace.

The other five advisories touch core components and storage drivers. Three need namespace-level write access or the right to create PersistentVolumes, and two only matter on Windows. None is rated above 6.5.

The September pair deserves attention from teams that give developers namespace-scoped rights. CVE-2026-2270 lets a user who can write StatefulSet and ControllerRevision objects in one namespace create a pod in another.

CVE-2026-76654 lets a pod on a Windows node make the kubelet authenticate to a network share the attacker controls, which hands over the hash of the kubelet's account.

Both are fixed in kubelet and kube-controller-manager 1.34.12, 1.35.9, 1.36.5 and 1.37.1, the patch releases of September 15, 2026.

Why does ingress-nginx keep showing up in Kubernetes security news?

Ingress-nginx routes outside traffic to workloads in a cluster, and the project describes it as one of the most popular Ingress controllers, built into many hosted Kubernetes platforms. It is also the component with the longest advisory record: 20 of the 95 entries in the project's feed, going back to February 2020.

The run of flaws that made the most news came on March 23, 2025, when the project published five ingress-nginx advisories together. The worst, CVE-2025-1974, scored 9.8 (Critical). The advisory says an unauthenticated attacker with access to the pod network could run code in the controller.

Wiz Research, which reported the flaws and called them IngressNightmare, said at the time that about 43% of cloud environments were vulnerable, and that it had found more than 6,500 clusters exposing the vulnerable admission controller to the internet.

On November 11, 2025, Kubernetes SIG Network and the Security Response Committee announced that ingress-nginx would be retired. Their post says the project had only one or two people doing development work for years, on their own time, and that the snippets annotations that once made it flexible had come to be seen as serious security flaws. It set the end of maintenance for March 2026 and pointed users to Gateway API or another Ingress controller.

The last advisory with an upstream fix, CVE-2026-4342, came on March 19, 2026.

The November advisory shows what retirement means in practice. CVE-2026-116472 is a low-severity flaw (2.7): a user allowed to create an Ingress can drop all traffic through the controller until it is restarted or reconfigured. The project published it and said it would not fix it.

The advisory names one patched build, from SUSE's own fork (version 1.15.2-prime1). It also gives a stopgap: an admission policy that rejects Ingresses using the mirror-target annotation, or a lower annotations-risk-level setting.

This flaw is minor. The next one may not be, and it will reach clusters still running the upstream controller with no patch at all.

Which Kubernetes versions still get security patches?

Kubernetes supports the three most recent minor releases, each for about a year. On November 15, 2026, the project's releases page lists 1.37, 1.36 and 1.35.

Minor releaseLatest patch (Sep 15, 2026)End of life
1.371.37.1October 28, 2027
1.361.36.5June 28, 2027
1.351.35.9February 28, 2027
1.341.34.12 (final)October 27, 2026
1.331.33.13 (final)June 28, 2026

Version 1.34 left support on October 27, 2026. A cluster still on 1.34 has the September fixes, but it will get none of the fixes that come after them.

Has any Kubernetes vulnerability been actively exploited?

Not according to CISA. KEV version 2026.11.13 holds 1,781 entries, and none is a CVE in a Kubernetes project component: not the API server, kubelet, kubectl, ingress-nginx or a CSI driver. The Kubernetes advisories themselves usually ask anyone who finds evidence of exploitation to report it to the project, and CVE-2025-1974's advisory said there were no known indicators of compromise.

The catalog does list exploited flaws in tools that sit next to clusters. One is Docker Desktop (CVE-2019-15752, a local privilege escalation, added November 3, 2021). The one that matters for 2026 is Trivy, Aqua Security's open-source vulnerability scanner. CISA added it on March 26, 2026, as an embedded malicious code flaw, with an April 9 deadline for federal agencies.

What happened in the Trivy supply-chain compromise?

Aqua Security's advisory (GHSA-69fq-xp46-6x23, CVE-2026-33634, rated critical) sets out two waves. On March 19, 2026, an attacker with compromised credentials published a malicious Trivy v0.69.4 release, force-pushed 76 of the 77 version tags of the trivy-action GitHub Action to credential-stealing code, and replaced all 7 tags of setup-trivy. On March 22 the attacker published malicious Trivy v0.69.5 and v0.69.6 images to Docker Hub.

The exposure windows were short, by the advisory's count: about 3 hours for the v0.69.4 binary, about 12 hours for trivy-action, about 4 hours for setup-trivy and about 10 hours for the Docker Hub images.

Short is not the same as harmless. A pipeline that pulled the bad build once ran code with the pipeline's own secrets in reach. The advisory lists who was not affected: users of Trivy v0.69.3 or earlier, images pinned by digest, binaries built from source, the official Homebrew formula, the trivy-action 0.35.0 tag, and trivy-action pinned to a commit made after April 9, 2025. Two of those protections come from settings any team can copy: GitHub's immutable releases, which Aqua had switched on in early March, and pinning dependencies by digest or commit instead of by tag.

What should a security team do with this?

  • Find ingress-nginx. The advisories give a one-line check: kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx. Any cluster that returns pods is running a controller with no upstream fixes left. Plan the move to Gateway API or another controller, or to a maintained fork, and treat the work as a security deadline, not a clean-up job.
  • Upgrade off 1.34 and older. The supported releases are 1.35, 1.36 and 1.37. A cluster on an end-of-life minor release receives no security fixes from the project.
  • Review namespace-scoped write rights. CVE-2026-2270 turns StatefulSet write access in one namespace into a pod in another. Patch to the September releases and check who holds those rights.
  • Patch Windows nodes and admin laptops. Two of 2026's five core advisories (CVE-2026-76654 and CVE-2026-19444) only affect Windows.
  • Pin build tools by digest or commit. The Trivy compromise reached pipelines that referenced tags. Pinned references and immutable releases kept others out. Rotate any secret a pipeline exposed between March 19 and 23, 2026, if it ran an affected Trivy component.
  • Watch the two feeds. The project's CVE feed is the authoritative list of Kubernetes advisories. CISA's catalog, tracked on this site's KEV tracker and must-patch window, shows when a flaw near the cluster is exploited. Aqua Security's KEV entry sits on its vendor page.

FAQ

What are the latest Kubernetes security vulnerabilities?

The newest advisory in the project's official CVE feed is CVE-2026-116472 (November 5, 2026), a low-severity ingress-nginx flaw that will not get an upstream fix. Before it came two September 14 advisories, CVE-2026-2270 (cross-namespace pod creation) and CVE-2026-76654 (NTLM hash theft on Windows nodes), fixed in 1.34.12, 1.35.9, 1.36.5 and 1.37.1.

Is ingress-nginx still supported?

No. Kubernetes ended ingress-nginx maintenance in March 2026, after announcing the retirement on November 11, 2025. Existing installations keep working, but the project issues no new releases or security fixes, as its November 2026 advisory confirms.

What was IngressNightmare?

IngressNightmare is the name Wiz Research gave to five ingress-nginx flaws the Kubernetes project disclosed on March 23, 2025. The worst, CVE-2025-1974, scored 9.8 and let an unauthenticated attacker on the pod network run code in the controller. Wiz said about 43% of cloud environments were vulnerable.

Is Kubernetes on the CISA KEV list?

No Kubernetes project component is on it. CISA's KEV catalog (version 2026.11.13) lists no CVE in Kubernetes itself, ingress-nginx, kubectl or the CSI drivers. It does list the Trivy scanner's March 2026 supply-chain compromise (CVE-2026-33634) and a 2019 Docker Desktop flaw.

Which Kubernetes versions are supported?

As of November 15, 2026, the project supports 1.37, 1.36 and 1.35, with end-of-life dates of October 28, 2027, June 28, 2027 and February 28, 2027. Version 1.34 reached end of life on October 27, 2026.

Methods note

The advisory counts come from the Kubernetes project's official CVE feed (JSON Feed format), fetched on November 15, 2026, with a refresh time of 06:24:57 UTC that day. The feed held 95 advisories. The publication date is each item's date_published field. The component is taken from the advisory's summary and text. The ingress-nginx count takes every advisory whose summary names ingress-nginx; the core components are the kubelet, kubectl and kube-controller-manager. CVSS scores are the base scores the advisories state; where an advisory gives only a vector, the table says so instead of computing a score. Year counts use the publication date, so CVE-2025-15566, published on February 6, 2026, counts in 2026.

The KEV figures come from CISA's KEV JSON feed, catalog version 2026.11.13 (released November 13, 2026, 1,781 entries). We searched every entry's vendor, product, name and description fields for Kubernetes components and common container tools. The counts will change as both feeds grow, and this page will be reviewed against them.

See also: the KEV glossary entry, CVE, CVSS, SBOM, the patch and vulnerability management hub, IoT Security News, OT Security News and Open Source Security News, which follows the wider TeamPCP campaign that began with Trivy.

Sources

  1. Kubernetes project (SIG Security, official CVE feed), published November 15, 2026 · primary source
  2. Kubernetes project (Security Response Committee), published November 5, 2026 · primary source
  3. Kubernetes project (SIG Network and Security Response Committee), published November 11, 2025 · primary source
  4. Kubernetes project, published September 15, 2026 · primary source
  5. Wiz Research, published March 24, 2025 · primary source
  6. CISA, published November 13, 2026 · primary source
  7. Aqua Security (GitHub security advisory for aquasecurity/trivy), published March 24, 2026 · primary source

By email, once a week

Get the week’s briefings on Friday

The week’s briefings and the new entries in CISA’s exploited-vulnerabilities catalog, in one email.

Unsubscribe any time.