VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/kubernetes/ingress-nginx: vulnerability history, versions and safety

github.com/kubernetes/ingress-nginx is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 34 releases, first recorded in Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/kubernetes/ingress-nginx vulnerabilities

Vulert verdict on github.com/kubernetes/ingress-nginx v0.0.0-20260319212116-5298c4d892ce i

Updated on 23 Oct 2026

Careful: v0.0.0-20260319212116-5298c4d892ce has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.0.0-20260319212116-5298c4d892ce — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 19 Aug 2024 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Stars 19,451 i
  • OpenSSF scorecard 5/10 i
  • Last release 7 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

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

Every version Vulert tracks for github.com/kubernetes/ingress-nginx, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20260319212116-5298c4d892ce 19 Mar 2026 U1 — No Details →
v0.0.0-20190306020402-ef0b1633e248 06 Mar 2019 U1 Apache-2.0 No Details →
v0.0.0-20190227172824-be1329b22580 27 Feb 2019 U1 Apache-2.0 No Details →
v0.0.0-20190214145133-b72dfa99d82b 14 Feb 2019 U1 Apache-2.0 No Details →
v0.0.0-20190203200103-3db1dc120260 03 Feb 2019 U1 Apache-2.0 No Details →
v0.0.0-20190118222239-42d3f6899286 18 Jan 2019 U1 Apache-2.0 No Details →
v0.0.0-20180926213817-50bb7897cfe2 26 Sep 2018 U1 Apache-2.0 No Details →
v0.0.0-20180102174842-da829748ecb5 02 Jan 2018 U1 Apache-2.0 No Details →
v0.0.0-20171111171658-fb33c58d188e 11 Nov 2017 U1 Apache-2.0 No Details →
v0.0.0-20171006202614-bf5616c65bca 06 Oct 2017 U1 Apache-2.0 No Details →
v0.0.0-20171006195836-2139ee85e7a7 06 Oct 2017 U1 Apache-2.0 No Details →
v0.0.0-20170823170251-0c6f15e372c8 23 Aug 2017 U1 Apache-2.0 No Details →
v0.0.0-20170803151325-fe19ebb09ee2 03 Aug 2017 U1 Apache-2.0 No Details →
v0.0.0-20170719140204-666bcca49573 19 Jul 2017 U1 Apache-2.0 No Details →
v0.0.0-20170131012608-3e87a2de40a1 31 Jan 2017 U1 Apache-2.0 No Details →
v0.0.0-20161129172144-81cd7782c65d 29 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161129171135-666cbf5089ee 29 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161129004117-f15c75a02d87 29 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161128014236-1bb8d1167380 28 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161127052804-478d51c8272c 27 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161125224342-d1fb96ac109a 25 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161125165557-f7bda48e7870 25 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161125132634-e51fe472c1d7 25 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161125132626-9dab90d7f2bd 25 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161125123245-cec1c9fb21b2 25 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161125122043-e374b0a9270b 25 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124081418-27a0ec41cc13 24 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124031305-61f124d786ab 24 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124003920-850af9329d8c 24 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124003430-16c580054509 24 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124001907-42b58e957c17 24 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124001749-5a8e09073683 24 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124001749-ed9a416b01a4 24 Nov 2016 U1 Apache-2.0 No Details →
v0.0.0-20161124001749-f2b627486d7f 24 Nov 2016 U1 Apache-2.0 No Details →

All 34 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/kubernetes/ingress-nginx

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-7646 in github.com/kubernetes/ingress-nginx N/A unrated No fix published 19 Aug 2024

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 github.com/kubernetes/ingress-nginx

Is github.com/kubernetes/ingress-nginx safe to use?

Vulert records 1 vulnerabilities for github.com/kubernetes/ingress-nginx in Go: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/kubernetes/ingress-nginx's Vulert package health score?

Vulert scores github.com/kubernetes/ingress-nginx 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/kubernetes/ingress-nginx affected?

Yes. v0.0.0-20260319212116-5298c4d892ce, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/kubernetes/ingress-nginx should I use?

v0.0.0-20260319212116-5298c4d892ce is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/kubernetes/ingress-nginx have?

1 vulnerability is recorded for github.com/kubernetes/ingress-nginx in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/kubernetes/ingress-nginx vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/kubernetes/ingress-nginx in the last 12 months, and the oldest entry in this database dates to 19 Aug 2024. 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 github.com/kubernetes/ingress-nginx 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 github.com/kubernetes/ingress-nginx for upcoming vulnerabilities?

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