Skip to content
Fencer Intel
high 8.8

CVE-2024-7646 in the critical feed json

CVE-2024-7646 in github.com/kubernetes/ingress-nginx

published 2y ago modified 4mo ago also EUVD-2024-48533 , GO-2024-3075

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
27.0%
EPSS 27.0% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

A security issue was discovered in ingress-nginx where an actor with permission to create Ingress objects (in the `networking.k8s.io` or `extensions` API group) can bypass annotation validation to inject arbitrary commands and obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.

Patch / fix

  • Kubernetes ingress-nginx 1.10.4, 1.11.2

Is CVE-2024-7646 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

27.02% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/kubernetes/ingress-nginx
all versions
no fix listed

Affected products

  • Kubernetes ingress-nginx

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.