CVE-2025-1097

CVE Enrichment

CVSS: 8.8 HIGH
EPSS: 33.24%
EPSS Percentile: 98.36%
CISA KEV: Not listed

Description

A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-cn` Ingress annotation can be used to inject configuration into nginx. This can lead to arbitrary code execution in the context of the ingress-nginx controller, and disclosure of Secrets accessible to the controller. (Note that in the default installation, the controller can access all Secrets cluster-wide.)

Technical Details

CVSS Version: 3.1
CNA / NVD Source: jordan@liggitt.net
Published: 25-Mar-2025 07:15
Last Modified: 17-Jun-2026 15:38
EPSS Date: 2026-10-16
CWE: CWE-20

CVSS Vector


            CVSS:3.1                            AV:N /
                            AC:L /
                            PR:L /
                            UI:N /
                            S:U /
                            C:H /
                            I:H /
                            A:H

References

Last enrichment sync: 17-Oct-2026 09:16
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (2)

Wiz Research discovered CVE-2025-1097, CVE-2025-1098, CVE-2025-24514 and CVE-2025-1974, a series of unauthenticated RCE vulnerabilities in Ingress NGINX Controller for Kubernetes dubbed #IngressNightmare. Exploitation Wiz’s Most-Read 2025 Research Highlights Supply-Chain Attacks, AI Exposure and Critical Vulnerabilities
Wiz Research discovered CVE-2025-1097, CVE-2025-1098, CVE-2025-24514 and CVE-2025-1974, a series of unauthenticated Remote Code Execution vulnerabilities in Ingress NGINX Controller for Kubernetes dubbed IngressNightmare Flaws Enable Unauthenticated RCE in Kubernetes Ingress NGINX

CVE (5)

Malware (3)

People (6)

MITRE ATT&CK (4)

Vendors (1)

Products (12)

Tools (2)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.