CVE-2025-1097

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 65.4%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 35%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.)

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
98.3%
KEV
Not listed

Published

March 25, 2025

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated May 22, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE - Multiple remote Exploit

https://www.exploit-db.com/exploits/52475
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20250328-0008/
generic

CVE-2025-1097: ingress-nginx controller configuration injection via unsanitized auth-tls-match-cn annotation · Issue #131007 · kubernetes/kubernetes · GitHub

https://github.com/kubernetes/kubernetes/issues/131007

Vendor Advisories for CVE-2025-1097(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
k8s.io/ingress-nginx———

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-18 10:03 UTCEPSS rescore
  7. 2026-07-16 17:02 UTCEPSS rescore
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 01:59 UTCEPSS rescore
  12. 2026-07-15 01:59 UTCEPSS rescore
  13. 2026-07-13 06:12 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-12 05:45 UTCEPSS rescore
  16. 2026-07-11 08:26 UTCEPSS rescore
  17. 2026-07-11 08:26 UTCEPSS rescore
  18. 2026-07-10 16:23 UTCOSV refresh
  19. 2026-07-09 19:09 UTCEPSS rescore
  20. 2026-07-08 15:14 UTCEPSS rescore
  21. 2026-07-06 16:26 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-01 15:06 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 66 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-24 14:04 UTCEPSS rescore
  5. 2026-06-24 14:04 UTCEPSS rescore
  6. 2026-06-23 21:32 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-21 01:59 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:52 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:48 UTCEPSS rescore
  14. 2026-06-14 23:17 UTCEPSS rescore
  15. 2026-06-13 22:59 UTCEPSS rescore
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-12 23:11 UTCEPSS rescore
  18. 2026-06-11 13:59 UTCEPSS rescore
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-08 14:16 UTCEPSS rescore
  21. 2026-06-08 14:16 UTCEPSS rescore
  22. 2026-06-06 13:47 UTCEPSS rescore
  23. 2026-06-06 13:47 UTCEPSS rescore
  24. 2026-06-05 22:46 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
  26. 2026-06-05 06:10 UTCEPSS rescore
  27. 2026-06-05 06:10 UTCEPSS rescore
  28. 2026-06-04 13:11 UTCEPSS rescore
  29. 2026-06-04 13:11 UTCEPSS rescore
  30. 2026-06-02 20:12 UTCEPSS rescore
  31. 2026-06-02 20:12 UTCEPSS rescore
  32. 2026-06-01 13:51 UTCEPSS rescore
  33. 2026-06-01 13:51 UTCEPSS rescore
  34. 2026-05-31 00:16 UTCEPSS rescore
  35. 2026-05-31 00:16 UTCEPSS rescore
  36. 2026-05-29 13:44 UTCEPSS rescore
  37. 2026-05-28 13:44 UTCEPSS rescore
  38. 2026-05-28 13:44 UTCEPSS rescore
  39. 2026-05-28 13:44 UTCEPSS rescore
  40. 2026-05-28 13:44 UTCEPSS rescore
  41. 2026-05-27 13:40 UTCEPSS rescore
  42. 2026-05-27 13:40 UTCEPSS rescore
  43. 2026-05-27 13:40 UTCEPSS rescore
  44. 2026-05-27 13:40 UTCEPSS rescore
  45. 2026-05-26 07:18 UTCEPSS rescore
  46. 2026-05-26 07:18 UTCEPSS rescore
  47. 2026-05-26 07:18 UTCEPSS rescore
  48. 2026-05-26 07:18 UTCEPSS rescore
  49. 2026-05-22 21:16 UTCEPSS rescore
  50. 2026-05-22 21:16 UTCEPSS rescore
  51. 2026-05-22 21:16 UTCEPSS rescore
  52. 2026-05-21 22:42 UTCEPSS rescore
  53. 2026-05-21 16:22 UTCEG score recompute
  54. 2026-05-21 16:22 UTCVendor advisory
  55. 2026-05-21 06:06 UTCOSV refresh
  56. 2026-05-20 22:37 UTCEPSS rescore
  57. 2026-05-20 22:37 UTCEPSS rescore
  58. 2026-05-20 22:37 UTCEPSS rescore
  59. 2026-05-20 22:37 UTCEPSS rescore
  60. 2026-05-20 22:37 UTCEPSS rescore
  61. 2026-05-20 11:21 UTCEPSS rescore
  62. 2026-05-20 11:21 UTCEPSS rescore
  63. 2026-05-20 11:21 UTCEPSS rescore
  64. 2026-05-20 11:21 UTCEPSS rescore
  65. 2026-05-20 11:21 UTCEPSS rescore
  66. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52475
    First seen Feb 4, 2026

    Ingress-NGINX Admission Controller v1.11.1 - FD Injection to RCE

    Open source ↗
  • GitHub PoClufeirider/IngressNightmare-PoC
    First seen Mar 30, 2025

    IngressNightmare-PoC： (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, CVE-2025-1974) PoC ，One-click script 。 一键脚本

    Open source ↗
  • GitHub PoChakaioffsec/IngressNightmare-PoC
    First seen Mar 26, 2025

    This is a PoC code to exploit the IngressNightmare vulnerabilities (CVE-2025-1097, CVE-2025-1098, CVE-2025-24514, and CVE-2025-1974).

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-1097.yaml
    First seen Jan 1, 2025

    Ingress-Nginx Controller - Configuration Injection via Unsanitized `auth-tls-match-cn` Annotation

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-1097?
CVE-2025-1097 is a high vulnerability published on March 25, 2025. 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…
When was CVE-2025-1097 disclosed?
CVE-2025-1097 was first published in the National Vulnerability Database on March 25, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-1097 actively exploited?
CVE-2025-1097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-1097?
CVE-2025-1097 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-1097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-1097, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-1097

Explore →

Is Your Infrastructure Affected by CVE-2025-1097?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs