{"answers":{"affected":"5 open source packages ship an affected version, including k8s.io/ingress-nginx.","exploited":"There is no known exploitation of CVE-2026-24512 in the wild and no public exploit code.","fix":"Upgrade k8s.io/ingress-nginx to a fixed version for your release line: 1.13.7 or 1.14.3.","what":"CVE-2026-24512 is a high-severity code injection vulnerability in Kubernetes ingress-nginx, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24512 and fix it if it is affected.\n\nWhat it is: CVE-2026-24512 is a high-severity code injection vulnerability in Kubernetes ingress-nginx, published on 3 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24512 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- k8s.io/ingress-nginx (Go): affected all versions; no fix listed\n- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.13.7\n- k8s.io/ingress-nginx (Go): affected all versions; fixed in 1.13.7\n- k8s.io/ingress-nginx (Go): affected from 1.14.0; fixed in 1.14.3\n- k8s.io/ingress-nginx (Go): affected from 1.14.0; fixed in 1.14.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24512/ (Markdown: https://insights.sbomify.com/CVE-2026-24512/index.md)","id":"CVE-2026-24512","markdown":"https://insights.sbomify.com/CVE-2026-24512/index.md","name":"CVE-2026-24512","record":{"aliases":["GHSA-jx8c-56mg-h6vp","GO-2026-4426","MINI-29mf-w34v-3vj7","MINI-48qr-98vv-rgg5","MINI-5658-rv8h-2xh2","MINI-5c58-pvm4-x96m","MINI-5wmc-5rcx-fp67","MINI-66cq-j487-jx7v","MINI-gp62-3qc3-r33r","MINI-p64f-gh7r-35r7","MINI-v953-j98v-q245","MINI-xfm8-2jrp-h34w"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes ingress controller","requires_auth":"low_privilege","summary":"Attackers can inject nginx configuration via Ingress paths, leading to arbitrary code execution and secret disclosure in the ingress-nginx controller.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"kubernetes","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"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.)","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ingress-nginx auth-method nginx configuration injection","id":"CVE-2026-24512","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":5,"n_references":1,"next":{"headline":"ingress-nginx auth-url protection bypass","id":"CVE-2026-24513"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":"pkg:golang/k8s.io/ingress-nginx","source":"GO-2026-4426"},{"ecosystem":"Go","fixed":["1.13.7"],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":null,"source":"GHSA-jx8c-56mg-h6vp"},{"ecosystem":"Go","fixed":["1.13.7"],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":"pkg:golang/k8s.io/ingress-nginx","source":"GHSA-jx8c-56mg-h6vp"},{"ecosystem":"Go","fixed":["1.14.3"],"introduced":["1.14.0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":null,"source":"GHSA-jx8c-56mg-h6vp"},{"ecosystem":"Go","fixed":["1.14.3"],"introduced":["1.14.0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":"pkg:golang/k8s.io/ingress-nginx","source":"GHSA-jx8c-56mg-h6vp"}],"prev":{"headline":"Information disclosure in PowerScale OneFS","id":"CVE-2026-24511"},"products":["ingress-nginx"],"published":"2026-02-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["Kubernetes"]},"summary":"Attackers can inject nginx configuration via Ingress paths, leading to arbitrary code execution and secret disclosure in the ingress-nginx controller.","url":"https://insights.sbomify.com/CVE-2026-24512/"}