CVE-2022-4886

Ingress-nginx `path` sanitization can be bypassed with `log_format` directive

Description

Ingress-nginx `path` sanitization can be bypassed with `log_format` directive.

Category

8.8
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.19%
Vendor Advisory github.com
Affected: Kubernetes ingress-nginx
Published at:
Updated at:

References

Link Tags
https://github.com/kubernetes/ingress-nginx/issues/10570 vendor advisory mitigation issue tracking
https://groups.google.com/g/kubernetes-security-announce/c/ge7u3qCwZLI mitigation mailing list
http://www.openwall.com/lists/oss-security/2023/10/25/5 third party advisory mailing list
https://security.netapp.com/advisory/ntap-20240307-0013/

Frequently Asked Questions

What is the severity of CVE-2022-4886?
CVE-2022-4886 has been scored as a high severity vulnerability.
How to fix CVE-2022-4886?
To fix CVE-2022-4886, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-4886 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-4886 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-4886?
CVE-2022-4886 affects Kubernetes ingress-nginx.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.