{}

{}

{}

{"acknowledgement": "Red Hat would like to thank Bruno Oliveira of IBM in collaboration with OpenAI for reporting this issue.", "bugzilla": {"description": "keycloak-services: keycloak-services: Stateless token preferred_username fallback enables identity rebinding", "id": "2539288", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2539288"}, "csaw": false, "cvss3": {"cvss3_base_score": "4.2", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N", "status": "draft"}, "cwe": "CWE-287", "details": ["A flaw was found in the TokenManager component of Keycloak, an open-source identity and access management solution. The issue occurs during the validation of stateless access tokens when the original user ID no longer exists. Keycloak incorrectly falls back to using the username to identify the user without verifying if the identity matches the original token subject. This could allow an attacker with an old token to gain access to a newly created service account if it shares the same client ID as a previously deleted one."], "mitigation": {"lang": "en:us", "value": "Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability."}, "name": "CVE-2026-96447", "package_state": [{"cpe": "cpe:/a:redhat:build_keycloak:", "fix_state": "Affected", "package_name": "keycloak-services", "product_name": "Red Hat Build of Keycloak"}, {"cpe": "cpe:/a:redhat:build_keycloak:", "fix_state": "Affected", "package_name": "rhbk/keycloak-rhel9", "product_name": "Red Hat Build of Keycloak"}, {"cpe": "cpe:/a:redhat:red_hat_single_sign_on:7", "fix_state": "Not affected", "package_name": "keycloak-services", "product_name": "Red Hat Single Sign-On 7"}], "public_date": "2026-11-05T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-96447\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-96447"], "statement": "The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires an administrator to delete and recreate a client with the same ID while an attacker holds a valid stateless token from the original client. Successful exploitation allows an attacker to gain the identity and permissions of the replacement service account. The vulnerability's root cause is an improper fallback to username-based resolution in stateless token validation without verifying the binding to the original token subject.", "threat_severity": "Moderate"}

{}