Ingress-nginx path can be pointed to service account token file

published 2022-05-06 4 y ago modified 2026-08-07 3 mo ago also GHSA-pvmg-xgmx-9mxh , EUVD-2022-4829

cvss: 7.6; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 distros 2

go k8s.io/ingress-nginx 1.2.0
Kubernetes Kubernetes ingress-nginx 1.2.0

opensuse arch linux

rke openSUSE Tumbleweed 1.3.10-1.1

opensuse advisories openSUSE-SU-2024:12031-1

kubectl-ingress-nginx Arch Linux 1.2.0-1

arch linux advisories AVG-2690

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-25745 updated 2026-03-27 cvss 7.6

k8s.io/ingress-nginx: 'path' can be pointed to service account token file

Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/management-ingress-rhel8
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.18% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.6	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:P/A:N
GitHub	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
go	k8s.io/ingress-nginx	<1.2.0	1.2.0

Affected products

Kubernetes Kubernetes ingress-nginx

Classification

Weakness

CWE-20 Improper Input Validation

Technology feeds

Kubernetes rss critical rss

References

groups.google.com /g/kubernetes-security-announce/c/7vQrpDZeBlc
web, issue-tracking, mailing-list, mitigation, third-party-advisory
github.com /kubernetes/ingress-nginx/issues/8502
web, issue-tracking, mitigation, third-party-advisory
security.netapp.com /advisory/ntap-20220609-0006/
third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2021-25745
advisory
github.com /kubernetes/ingress-nginx
package
security.netapp.com /advisory/ntap-20220609-0006
web

Sources

Fencer Vulns 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.

Summary