CVE-2026-24512: ingress-nginx auth-method nginx configuration injection

Published Feb 3, 2026
·
Updated

A security issue was discovered in ingress-nginx cthe rules.http.paths.path Ingress field 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.)

Other sources

A security issue was discovered in ingress-nginx where the rules.http.paths.path Ingress field 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.)

— MITRE

A security issue was discovered in ingress-nginx. Tthe rules.http.paths.path Ingress field 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.)

— GitHub

Affected Software

4 affected componentsFixes available
k8s/ingress-nginx
go/k8s.io/ingress-nginx>=1.14.0<1.14.3
1.14.3
go/k8s.io/ingress-nginx<1.13.7
1.13.7
IBM API Connect V12 OnPrem<=v12.1.0.0 - v12.1.1.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/k8s.io/ingress-nginx to a version that resolves this vulnerability.

    Fixed in 1.14.3
  2. Upgrade

    Upgrade go/k8s.io/ingress-nginx to a version that resolves this vulnerability.

    Fixed in 1.13.7

Event History

Feb 3, 2026
CVE Published
via MITRE·10:17 PM
Data Sourced
via MITRE·10:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeakness
Feb 4, 2026
Advisory Published
via GitHub·12:30 AM
Data Sourced
via GitHub·12:30 AM
DescriptionSeverityWeaknessAffected Software
Oct 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-24512?

CVE-2026-24512 is considered a critical vulnerability due to the potential for arbitrary code execution.

2

How do I fix CVE-2026-24512?

To fix CVE-2026-24512, you should upgrade to the latest version of ingress-nginx that addresses this vulnerability.

3

What impact does CVE-2026-24512 have on my system?

CVE-2026-24512 can lead to arbitrary code execution and potential disclosure of sensitive information in the context of the ingress-nginx controller.

4

What versions of ingress-nginx are affected by CVE-2026-24512?

CVE-2026-24512 impacts all versions of ingress-nginx that allow for configuration injection through the `rules.http.paths.path` Ingress field.

5

How does CVE-2026-24512 allow configuration injection?

CVE-2026-24512 enables configuration injection through improper sanitization of the `rules.http.paths.path` field, allowing attackers to manipulate nginx configurations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203