CVE-2022-4886 json
Ingress-nginx `path` sanitization can be bypassed with `log_format` directive
published 2023-10-25 3 y ago modified 2026-08-07 3 mo ago also GHSA-gvrm-w2f9-f77q , EUVD-2023-2743
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Ingress-nginx `path` sanitization can be bypassed with `log_format` directive.
Patch / fix
- go k8s.io/ingress-nginx 1.8.0
- Kubernetes ingress-nginx 1.8.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 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 | k8s.io/ingress-nginx | <1.8.0 |
1.8.0 |
Affected products
- Kubernetes ingress-nginx
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
github.com
/kubernetes/ingress-nginx/issues/10570
issue-tracking, web, mitigation, vendor-advisory
-
groups.google.com
/g/kubernetes-security-announce/c/ge7u3qCwZLI
mailing-list, web, mitigation
-
openwall.com
/lists/oss-security/2023/10/25/5
web, mailing-list, third-party-advisory
- security.netapp.com /advisory/ntap-20240307-0013/
-
nvd.nist.gov
/vuln/detail/CVE-2022-4886
advisory
-
github.com
/kubernetes/ingress-nginx
package
-
security.netapp.com
/advisory/ntap-20240307-0013
web
Sources
- CVE List CVE-2022-4886
- GitHub Advisory GHSA-gvrm-w2f9-f77q
- NVD CVE-2022-4886
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.