Aller au contenu
2.7 Faible

CVE-2026-116472 ingress-nginx mirror-target self-DOS

Description

A security issue was discovered in ingress-nginx where a user with permission to create an Ingress may be able to cause denial of service of the ingress-nginx data plane, or possibly redirect traffic from other Ingresses. Kubernetes clusters are only affected if they are using ingress-nginx. Due to a missing check, the mirror-target Ingress annotation can be used to target an unauthenticated configuration API within the ingress-nginx controller, allowing write commands to be submitted. Corrupting the data within that configuration API results in all traffic through ingress-nginx being dropped until an Ingress configuration change or a controller restart causes the data to be recreated correctly. In principle, this write access could also be used to redirect traffic from other Ingresses controlled by the same ingress-nginx instance. In practice, there is negligible additional risk: such redirection would require privileged information about internal ingress-nginx state, and users can already redirect traffic from other Ingresses controlled by the same ingress-nginx anyway.

Détail CVSS 3.1

Vecteur CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L

Exploitable à distance par le réseau, avec un compte administrateur et sans action d’un utilisateur ; l’impact sur les données ou le service reste limité.

Vecteur d’attaque
Réseau
Complexité
Faible
Privilèges requis
Élevés
Interaction
Aucune
Portée
Inchangée
Confidentialité
Aucun
Intégrité
Aucun
Disponibilité
Faible

Produits et versions touchés

Produit Versions touchées Corrigé en
ingress-nginx Versions non publiées
Rancher Prime RKE2 ingress-nginx 1.15 premières → < 1.15.2-prime1 1.15.2-prime1
Les 18 CVE de ingress-nginx →
Suivre cette CVE