CVE-2026-1035

{"id": "CVE-2026-1035", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "secalert@redhat.com", "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:N/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "NONE", "privilegesRequired": "LOW", "confidentialityImpact": "NONE"}, "impactScore": 1.4, "exploitabilityScore": 1.6}]}, "published": "2026-01-21T06:15:46.937", "references": [{"url": "https://access.redhat.com/errata/RHSA-2026:6477", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/errata/RHSA-2026:6478", "source": "secalert@redhat.com"}, {"url": "https://access.redhat.com/security/cve/CVE-2026-1035", "source": "secalert@redhat.com"}, {"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2430314", "source": "secalert@redhat.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "secalert@redhat.com", "description": [{"lang": "en", "value": "CWE-367"}]}], "descriptions": [{"lang": "en", "value": "A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This allows concurrent refresh requests to bypass single-use enforcement and issue multiple access tokens from the same refresh token. As a result, Keycloak\u2019s refresh token rotation hardening can be undermined."}, {"lang": "es", "value": "Se encontr\u00f3 una falla en el servidor Keycloak durante el procesamiento de tokens de actualizaci\u00f3n, espec\u00edficamente en la clase TokenManager responsable de aplicar las pol\u00edticas de reutilizaci\u00f3n de tokens de actualizaci\u00f3n. Cuando la rotaci\u00f3n estricta de tokens de actualizaci\u00f3n est\u00e1 habilitada, la validaci\u00f3n y actualizaci\u00f3n del uso del token de actualizaci\u00f3n no se realizan de forma at\u00f3mica. Esto permite que las solicitudes de actualizaci\u00f3n concurrentes eludan la aplicaci\u00f3n del uso \u00fanico y emitan m\u00faltiples tokens de acceso desde el mismo token de actualizaci\u00f3n. Como resultado, el endurecimiento de la rotaci\u00f3n de tokens de actualizaci\u00f3n de Keycloak puede verse socavado."}], "lastModified": "2026-04-15T00:35:42.020", "sourceIdentifier": "secalert@redhat.com"}