← 返回列表

CVE-2025-15566

单站 Kubernetes Vulnerability Announcements 发布 Fri, 06 Feb 2026 02:54:24 +0000 入库 2026-11-18T06:56:48

Repository navigation

area/security

committee/security-responseDenotes an issue or PR intended to be handled by the product security committee.Denotes an issue or PR intended to be handled by the product security committee.

kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.

official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)

sig/networkCategorizes an issue or PR as relevant to SIG Network.Categorizes an issue or PR as relevant to SIG Network.

triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.

Description

on Feb 5, 2026

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

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.)

Am I vulnerable?

This issue affects ingress-nginx. If you do not have ingress-nginx installed on your cluster, you are not affected. You can check this by running kubectl get pods --all-namespaces --selector app.kubernetes.io/name=ingress-nginx.

Affected Versions

How do I mitigate this vulnerability?

ACTION REQUIRED: The following steps must be taken to mitigate this vulnerability: Upgrade ingress-nginx to v1.12.5, v1.13.1, or any later version.

How to upgrade?

To upgrade, refer to the documentation: Upgrading Ingress-nginx

Detection

Suspicious data within a configmap passed to the nginx.ingress.kubernetes.io/auth-proxy-set-headers annotation of an Ingress resource could indicate an attempt to exploit this vulnerability.

If you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io

Acknowledgements

This issue was discovered and patched by Jan-Otto Kröpke.

/area security

/kind bug

/committee security-response

/label official-cve-feed

/sig network

OSV format

{
  "schema_version": "1.6.0",
  "id": "CVE-2025-15566",
  "modified": "2026-02-06T02:46:50Z",
  "summary": "ingress-nginx auth-proxy-set-headers nginx configuration injection",
  "details": "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.)",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Kubernetes",
        "name": "ingress-nginx"
      },
      "ranges": [
        {
          "type": "SEMVER",
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "v1.12.5"
            },
            {
              "introduced": "0"
            },
            {
              "fixed": "v1.13.1"
            }
          ]
        }
      ]
    }
  ],
  "references": [
    {
      "type": "WEB",
      "url": "https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "credits": [
    {
      "name": "This issue was discoverd **and patched** by Jan-Otto Kröpke.",
      "type": "FINDER"
    }
  ]
}

Activity

  1. k8s-ci-robotadded kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.committee/security-responseDenotes an issue or PR intended to be handled by the product security committee.Denotes an issue or PR intended to be handled by the product security committee.sig/networkCategorizes an issue or PR as relevant to SIG Network.Categorizes an issue or PR as relevant to SIG Network.official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.on Feb 5, 2026
  2. tabbysable commentedon Feb 5, 2026 MemberAuthorMore actions Note that this issue is documenting a vulnerability that was fixed in previous versions of ingress-nginx, released in August 2025.

  3. tabbysable commentedon Feb 5, 2026 MemberAuthorMore actions /triage accepted

  4. k8s-ci-robotadded triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on. and removed needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.on Feb 5, 2026
  5. tabbysable commentedon Feb 5, 2026 MemberAuthorMore actions /close

  6. k8s-ci-robotclosed this as completedon Feb 5, 2026
  7. k8s-ci-robot commentedon Feb 5, 2026 ContributorMore actions @tabbysable: Closing this issue. ## Details In response to this:


    /close Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
  8. sathieu commentedon Feb 9, 2026 More actions @tabbysable Affected versions should be changed to:

    • ingress-nginx: prior to v1.12.5
    • ingress-nginx: v1.13.x, prior to v1.13.1

Reacted by Naimuddin Shaik and Madhava Kulkarni
9. ### tabbysable commentedon Feb 11, 2026 MemberAuthorMore actions Oh good call, thank you @sathieu, there was a formatting error that caused the < to get lost.
Reacted by Mathieu Parent

Metadata

Metadata

Assignees

Labels

area/security

committee/security-responseDenotes an issue or PR intended to be handled by the product security committee.Denotes an issue or PR intended to be handled by the product security committee.

kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.

official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)

sig/networkCategorizes an issue or PR as relevant to SIG Network.Categorizes an issue or PR as relevant to SIG Network.

triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.

原文链接:https://github.com/kubernetes/kubernetes/issues/136789