CVE-2025-1097: ngress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation

CVE-2025-1097 · Severity: low · CVSS 3.1 · Published 2025-03-25

ngress-nginx controller - configuration injection via unsanitized auth-tls-match-cn annotation in k8s.io/ingress-nginx

Technologies: k8s.io/ingress-nginx (Go). Vendors: Go.

Quick answers

Is CVE-2025-1097 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-1097 being exploited in the wild.
How severe is CVE-2025-1097?
Low severity, with a CVSS score of 3.1, published 25 March 2025.
Which products and versions are affected?
k8s.io/ingress-nginx (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=1.11.5.
Is there a fix for CVE-2025-1097?
Yes. k8s.io/ingress-nginx (Go): upgrade to 1.11.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-1097?
Check whether you run k8s.io/ingress-nginx (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • k8s.io/ingress-nginx (Go): upgrade to 1.11.5 or later
    go get k8s.io/ingress-nginx@v1.11.5

Affected products

  • k8s.io/ingress-nginx (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=1.11.5

Identifiers

  • CVE-2025-1097
  • GHSA-823x-fv5p-h7hw
  • GO-2025-3565

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.