{"answers":{"affected":"5 open source packages ship an affected version, including k8s.io/ingress-nginx.","exploited":"There is no known exploitation of CVE-2026-24513 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-24513 is a low-severity authentication bypass 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-24513 and fix it if it is affected.\n\nWhat it is: CVE-2026-24513 is a low-severity authentication bypass 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-24513 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-24513/ (Markdown: https://insights.sbomify.com/CVE-2026-24513/index.md)","id":"CVE-2026-24513","markdown":"https://insights.sbomify.com/CVE-2026-24513/index.md","name":"CVE-2026-24513","record":{"aliases":["GHSA-4g2f-xcph-2335","GO-2026-4419","MINI-295q-hc5x-vvr3","MINI-2jv5-fcfc-jp92","MINI-4c88-ppm7-gh6w","MINI-5ggr-c74h-p5x2","MINI-c92g-5w33-c8q3","MINI-pm9f-f8j7-66h3","MINI-pvqh-mj6p-f4cx","MINI-rcrp-pr4g-34cr","MINI-w72g-4x9x-3pqf","MINI-xhp4-p864-2cjm"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Kubernetes ingress controller","requires_auth":"low_privilege","summary":"Attackers can bypass authentication in ingress-nginx if a custom error backend ignores the X-Code header, requiring specific non-default configuration.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"kubernetes","cpe":[],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in the presence of a specific misconfiguration.\n\nIf the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the `auth-url` annotation may be accessed even when authentication fails.\n\nNote that the built-in custom-errors backend works correctly. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component.","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-url protection bypass","id":"CVE-2026-24513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":5,"n_references":1,"next":{"headline":"ingress-nginx Admission Controller denial of service","id":"CVE-2026-24514"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":"pkg:golang/k8s.io/ingress-nginx","source":"GO-2026-4419"},{"ecosystem":"Go","fixed":["1.13.7"],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":null,"source":"GHSA-4g2f-xcph-2335"},{"ecosystem":"Go","fixed":["1.13.7"],"introduced":["0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":"pkg:golang/k8s.io/ingress-nginx","source":"GHSA-4g2f-xcph-2335"},{"ecosystem":"Go","fixed":["1.14.3"],"introduced":["1.14.0"],"last_affected":[],"package":"k8s.io/ingress-nginx","purl":null,"source":"GHSA-4g2f-xcph-2335"},{"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-4g2f-xcph-2335"}],"prev":{"headline":"ingress-nginx auth-method nginx configuration injection","id":"CVE-2026-24512"},"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":"partial"},"state":"PUBLISHED","updated":"2026-02-18","vendors":["Kubernetes"]},"summary":"Attackers can bypass authentication in ingress-nginx if a custom error backend ignores the X-Code header, requiring specific non-default configuration.","url":"https://insights.sbomify.com/CVE-2026-24513/"}