Vulnerability Database · Bitnami · Package report

nginx-ingress-controller: vulnerability history, versions and safety

nginx-ingress-controller is a package in the Bitnami ecosystem. Vulert records 27 vulnerabilities for it across 16 affected ranges, from Nov 2023 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
27 vulnerabilities recorded C1 H18 M7 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
7 in the last 12 months

Most recent disclosure 23 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on nginx-ingress-controller i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 23 Mar 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 27 vulnerabilities on record across 2 years, 7 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 27 over 2 years · 7 in the last year i
  • Latest disclosure 23 Mar 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 1.0.0 up to 2.3.0 (exclusive) 1
up to 1.14.2 (exclusive) 4
from 1.13.0 up to 1.13.9 (exclusive) 1
up to 1.13.8 (exclusive) 1
up to 1.13.1 (exclusive) 1
from 1.9.0 up to 1.12.4 (exclusive) 3
from 1.0.0 up to 1.12.3 (exclusive) 1
up to 1.11.7 (exclusive) 5
up to 1.11.2 (exclusive) 1
up to 1.9.3 (exclusive) 1
up to 1.9.0 (exclusive) 2
up to 1.8.0 (exclusive) 1
up to 1.2.1 (exclusive) 1
up to 1.2.0 (exclusive) 2
up to 0.49.1 (exclusive) 1
up to 0.28.0 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 5
  • 2024 10
  • 2025 5
  • 2026 7

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 7 of the 27 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About nginx-ingress-controller

Is nginx-ingress-controller safe to use?

Vulert records 27 vulnerabilities for nginx-ingress-controller in Bitnami: 1 critical, 18 high, 7 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does nginx-ingress-controller have?

27 vulnerabilities are recorded for nginx-ingress-controller in the Bitnami ecosystem: 1 critical, 18 high, 7 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new nginx-ingress-controller vulnerabilities disclosed?

7 vulnerabilities were recorded for nginx-ingress-controller in the last 12 months, and the oldest entry in this database dates to 06 Nov 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of nginx-ingress-controller are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor nginx-ingress-controller for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the nginx-ingress-controller version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.