← 返回列表

CVE-2026-4342

单站 Kubernetes Vulnerability Announcements 发布 Thu, 19 Mar 2026 14:32:54 +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.

lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.

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 Mar 19, 2026

CVSS Rating: 8.8 (Medium) 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 a combination of Ingress annotations 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?

How to upgrade?

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

Detection

Suspicious data within the rules.http.paths.path field 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 vulnerability was reported by wooseokdotkim.

/triage accepted

/lifecycle frozen

/area security

/kind bug

/committee security-response

OSV format

{
  "schema_version": "1.6.0",
  "id": "CVE-2026-4342",
  "modified": "2026-03-19T17:11:29Z",
  "summary": "ingress-nginx comment-based nginx configuration injection",
  "details": "A security issue was discovered in ingress-nginx where a combination of Ingress annotations 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.13.9"
            },
            {
              "introduced": "0"
            },
            {
              "fixed": "v1.14.5"
            },
            {
              "introduced": "0"
            },
            {
              "fixed": "v1.15.1"
            }
          ]
        }
      ]
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/cverecord?id=CVE-2026-4342"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/kubernetes/kubernetes/issues/137893"
    },
    {
      "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 vulnerability was reported by wooseokdotkim.",
      "type": "FINDER"
    }
  ]
}

Activity

  1. k8s-ci-robotadded lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.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.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.on Mar 19, 2026
  2. Siddartha-DevOps commentedon Mar 19, 2026 More actions @k8s-ci-robot @tabbysable


    Can you please clarify if this placeholder issue corresponds to a specific CVE or security advisory, and when more details will be published? if guidance is provided, I can help giving my full-time availability to this issue.
  3. tabbysablechanged the title ~~[-]Placeholder Issue[/-]~~ [+]CVE-2026-4342: ingress-nginx comment-based nginx configuration injection[/+] on Mar 19, 2026
  4. tabbysable commentedon Mar 19, 2026 MemberAuthorMore actions /label official-cve-feed


    /sig network
  5. k8s-ci-robotadded 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)on Mar 19, 2026
  6. tabbysable commentedon Mar 19, 2026 MemberAuthorMore actions Fix PR: kubernetes/ingress-nginx#14728


    As is our policy, this announcement is being made along with the public release of the fix source code. Release builds for v1.15.1, v1.14.5, and v1.13.9 are in progress. I will update the ticket when they are available.
  7. tabbysable commentedon Mar 19, 2026 MemberAuthorMore actions Release builds have finished, and the patched versions are available from all the usual places. Special thanks to @Gacko, @Stevenjin8, and @strongjz for their hustle to get this fix written, tested, and published before KubeCon. It has been a wonderful pleasure to work with you to give all ingress-nginx users the cleanest, safest final release we possibly can.


    /honk
    /close
    Reacted by Steven Jin, Luis de Niz, Tim and Jintao Zhang
  8. k8s-ci-robot commentedon Mar 19, 2026 ContributorMore actions @tabbysable:

Details In response to this:

Release builds have finished, and the patched versions are available from all the usual places. Special thanks to @Gacko, @Stevenjin8, and @strongjz for their hustle to get this fix written, tested, and published before KubeCon. It has been a wonderful pleasure to work with you to give all ingress-nginx users the cleanest, safest final release we possibly can.
/honk
/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.
9. ### k8s-ci-robot commentedon Mar 19, 2026 ContributorMore actions @tabbysable: Closing this issue.

Details In response to this:

Release builds have finished, and the patched versions are available from all the usual places. Special thanks to @Gacko, @Stevenjin8, and @strongjz for their hustle to get this fix written, tested, and published before KubeCon. It has been a wonderful pleasure to work with you to give all ingress-nginx users the cleanest, safest final release we possibly can.
/honk
/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.
10. k8s-ci-robotclosed this as completedon Mar 19, 2026
11. ### Siddartha-DevOps commentedon Mar 19, 2026 More actions thanks for confirming
12. ### sathieu commentedon Mar 23, 2026 More actions Is {{ $server.Hostname }} safe ? Shouldn't it be removed from comment too?
Reacted by Tomasz Dłuski and bert boerland
13. ### Toumash commentedon Apr 8, 2026 More actions Is {{ $server.Hostname }} safe ? Shouldn't it be removed from comment too?
i was about to ask the same. How is this a vulnerability if you give cluster rights to untrusted individuals/apps and allow malicious inputs in the plain text?
Then the rest of the config is basically a new CVE same as $location.ExternalAuth.
No?
14. ### tombokombo commentedon Apr 14, 2026 More actions ingress hostname is validated by regex [a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*, so it is safe
Reacted by Tomasz Dłuski

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.

lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.

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/137893