CVE-2026-24513

{"id": "CVE-2026-24513", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "jordan@liggitt.net", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 3.1, "attackVector": "NETWORK", "baseSeverity": "LOW", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "LOW"}, "impactScore": 1.4, "exploitabilityScore": 1.6}]}, "published": "2026-02-03T23:16:07.130", "references": [{"url": "https://github.com/kubernetes/kubernetes/issues/136679", "source": "jordan@liggitt.net"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "jordan@liggitt.net", "description": [{"lang": "en", "value": "CWE-754"}]}], "descriptions": [{"lang": "en", "value": "A security issue was discovered in ingress-nginx\u00a0where 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."}, {"lang": "es", "value": "Se descubri\u00f3 un problema de seguridad en ingress-nginx donde la protecci\u00f3n ofrecida por la anotaci\u00f3n Ingress 'auth-url' podr\u00eda no ser efectiva en presencia de una configuraci\u00f3n err\u00f3nea espec\u00edfica.\n\nSi el controlador ingress-nginx est\u00e1 configurado con una configuraci\u00f3n predeterminada de errores personalizados que incluye errores HTTP 401 o 403, y si el backend predeterminado de errores personalizados configurado es defectuoso y no respeta el encabezado HTTP X-Code, entonces se podr\u00eda acceder a un Ingress con la anotaci\u00f3n 'auth-url' incluso cuando la autenticaci\u00f3n falla.\n\nTenga en cuenta que el backend de errores personalizados integrado funciona correctamente. Para activar este problema se requiere que un administrador configure espec\u00edficamente ingress-nginx con un componente externo defectuoso."}], "lastModified": "2026-04-15T00:35:42.020", "sourceIdentifier": "jordan@liggitt.net"}