CVE-2025-15566

Published Feb 6, 2026

Last updated 2 months ago

CVSS high 8.8
Kubernetes
ingress-nginx
Container Security

Overview

Description
A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/auth-proxy-set-headers` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)
Source
jordan@liggitt.net
NVD status
Awaiting Analysis

Risk scores

CVSS 3.1

Type
Secondary
Base score
8.8
Impact score
5.9
Exploitability score
2.8
Vector string
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

jordan@liggitt.net
CWE-20

Social media

Hype score
Not currently trending

  1. CVE-2025-15566 (CVSS:8.8, HIGH) is Awaiting Analysis. A security issue was discovered in ingress-nginx where the `https://t.co/ck5lZ1DrME` Ingress ..https://t.co/uKT90IxpUB #cybersecurityawareness #cybersecurity #CVE #infosec #hacker #nvd #mitre

    @cracbot

    11 Feb 2026

    9 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. no this cve, CVE-2025-15566 is not from the set earlier this week - this is just the non-stop security nightmare that is kubernetes https://t.co/jIcxg8dr0D

    @nanovms

    6 Feb 2026

    186 Impressions

    2 Retweets

    3 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. CVE-2025-15566 #devopsish #kubernetes #cve https://t.co/mIyVR7HGKV

    @ChrisShort

    6 Feb 2026

    119 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  4. CVE-2025-15566: ingress-nginx auth-proxy-set-headers nginx configuration injection - https://t.co/fmNcoelbFa

    @kubernetesio

    6 Feb 2026

    5080 Impressions

    7 Retweets

    33 Likes

    17 Bookmarks

    3 Replies

    0 Quotes

  5. CVE-2025-15566: ingress-nginx auth-proxy-set-headers nginx configuration injection - https://t.co/w1VtoO3WAv

    @K8sContributors

    6 Feb 2026

    727 Impressions

    1 Retweet

    11 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  6. CVE-2025-15566 Kubernetes Ingress-Nginx Arbitrary Code Execution via Header Injection Annotation https://t.co/13fssoOBrk

    @VulmonFeeds

    6 Feb 2026

    84 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  7. CVE-2025-15566 A security issue was discovered in ingress-nginx where the `https://t.co/5vaSyCfUF2` Ingress annotation can be used to inject configuration… https://t.co/iXN8vewOdK

    @CVEnew

    6 Feb 2026

    206 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

Related CVEs

  1. Docker Model Runner (DMR) is software used to manage, run, and deploy AI models using Docker. Versions prior to 1.0.16 expose a POST `/engines/_configure` endpoint that accepts arbitrary runtime flags without authentication. These flags are passed directly to the underlying inference server (llama.cpp). By injecting the --log-file flag, an attacker with network access to the Model Runner API can write or overwrite arbitrary files accessible to the Model Runner process. When bundled with Docker Desktop (where Model Runner is enabled by default since version 4.46.0), it is reachable from any default container at model-runner.docker.internal without authentication. In this context, the file overwrite can target the Docker Desktop VM disk (`Docker.raw` ), resulting in the destruction of all containers, images, volumes, and build history. However, in specific configurations and with user interaction, it is possible to convert this vulnerability in a container escape. The issue is fixed in Docker Model Runner 1.0.16. Docker Desktop users should update to 4.61.0 or later, which includes the fixed Model Runner. A workaround is available. For Docker Desktop users, enabling Enhanced Container Isolation (ECI) blocks container access to Model Runner, preventing exploitation. However, if the Docker Model Runner is exposed to localhost over TCP in specific configurations, the vulnerability is still exploitable.•CVE-2026-28400
  2. An out of bounds read vulnerability in the grpcfuse kernel module present in the Linux VM in Docker Desktop for Windows, Linux and macOS up to version 4.61.0 could allow a local attacker to cause an unspecified impact by writing to /proc/docker entries. The issue has been fixed in Docker Desktop 4.62.0 .•CVE-2026-2664
  3. A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in the presence of a specific misconfiguration. If the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the `auth-url` annotation may be accessed even when authentication fails. Note that the built-in custom-errors backend works correctly. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component.•CVE-2026-24513
  4. A security issue was discovered in ingress-nginx where the validating admission controller feature is subject to a denial of service condition. By sending large requests to the validating admission controller, an attacker can cause memory consumption, which may result in the ingress-nginx controller pod being killed or the node running out of memory.•CVE-2026-24514
  5. A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/auth-method` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)•CVE-2026-1580

References

Sources include official advisories and independent security research.