Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,288
Published in 7 days
1,836
Critical in 30 days
487
Actively exploited
542
Clear filters

Results for “Ingress NGINX Controller”

10 vulnerabilities
  1. Low 2.7

    CVE-2026-116472 · Ingress NGINX Controller

    ingress-nginx mirror-target self-DOS

    Published 5 Nov 2026 · CVE Program
  2. High 8.8

    CVE-2026-3288 · Ingress NGINX Controller

    A security issue was discovered in ingress-nginx where the `nginx.ingress.kubernetes.io/rewrite-target` 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…

    Published 9 Mar 2026 · Fixed in 1.13.8, 1.14.4 · NVD
  3. High 8.8

    CVE-2023-5044 · Ingress NGINX Controller

    Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation.

    Published 25 Oct 2023 · Fixed in 1.9.0 · NVD
  4. High 8.8

    CVE-2023-5043 · Ingress NGINX Controller

    Ingress nginx annotation injection causes arbitrary command execution.

    Published 25 Oct 2023 · Fixed in 1.9.0 · NVD
  5. Medium 6.5

    CVE-2022-4886 · Ingress NGINX Controller

    Ingress-nginx `path` sanitization can be bypassed with `log_format` directive.

    Published 25 Oct 2023 · Fixed in 1.8.0 · NVD
  6. Medium 6.5

    CVE-2021-25748 · Ingress NGINX Controller

    A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use a newline character to bypass the sanitization of the `spec.rules[].http.paths[].path` field of an Ingress object (in the `networking.k8s.io` or `extensions` API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access…

    Published 24 May 2023 · Fixed in 1.2.1 · NVD
  7. High 7.1

    CVE-2021-25746 · Ingress NGINX Controller

    A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use .metadata.annotations in an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.

    Published 6 May 2022 · Fixed in 1.2.0 · NVD
  8. High 8.1

    CVE-2021-25745 · Ingress NGINX Controller

    A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the spec.rules[].http.paths[].path field of an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.

    Published 6 May 2022 · Fixed in 1.2.0 · NVD
  9. High 7.1

    CVE-2021-25742 · Ingress NGINX Controller

    A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the custom snippets feature to obtain all secrets in the cluster.

    Published 29 Oct 2021 · Fixed in 0.49.1 · NVD
  10. Medium 5.9

    CVE-2020-8553 · Ingress NGINX Controller

    The Kubernetes ingress-nginx component prior to version 0.28.0 allows a user with the ability to create namespaces and to read and create ingress objects to overwrite the password file of another ingress which uses nginx.ingress.kubernetes.io/auth-type: basic and which has a hyphenated namespace or secret name.

    Published 29 Jul 2020 · Fixed in 0.28.0 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.