{"id":"CVE-2026-96447","aliases":[],"summary":"Keycloak-services: keycloak-services: stateless token preferred_username fallback enables identity rebinding","published_at":"2026-11-05T00:00:00Z","modified_at":"2026-11-19T21:36:50.798Z","products":[{"slug":"keycloak","name":"Keycloak","category":"identity"}],"rating":{"severity":"medium","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","attack_path":"internet_authenticated","user_interaction":false,"malicious":false,"red_hat":"Moderate","vendor_ratings":[{"source":"Red Hat","rating":"Moderate"}]},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.002259999979287386,"percentile":0.1351899951696396,"date":"2026-11-19T00:00:00Z"},"priority":5.2,"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.","affected_stack":[{"ecosystem":"CVE","package":"Red Hat/Red Hat build of Keycloak 26.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.6.8-2"}]}],"fixed":["26.6.8-2"],"provider":"cvelistv5","source":"CVE-2026-96447","relation":"self"},{"ecosystem":"CVE","package":"Red Hat/Red Hat build of Keycloak 26.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.6-24"}]}],"fixed":["26.6-24"],"provider":"cvelistv5","source":"CVE-2026-96447","relation":"self"},{"ecosystem":"CVE","package":"Red Hat/Red Hat build of Keycloak 26.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.6-24"}]}],"fixed":["26.6-24"],"provider":"cvelistv5","source":"CVE-2026-96447","relation":"self"}],"affected_other":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat Single Sign-On 7","cpe":"cpe:/a:redhat:red_hat_single_sign_on:7","status":"not_affected","packages":["keycloak-services"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-96447"},{"vendor":"Red Hat","product":"Red Hat build of Keycloak 26.6","cpe":"cpe:/a:redhat:build_keycloak:26.6::el9","status":"fixed","packages":["rhbk/keycloak-operator-bundle","rhbk/keycloak-rhel9","rhbk/keycloak-rhel9-operator"],"package_count":3,"fixed":[],"advisories":["RHSA-2026:95762"],"provider":"redhat-vex","source":"CVE-2026-96447"},{"vendor":"Red Hat","product":"Red Hat build of Keycloak 26.6.8","cpe":"cpe:/a:redhat:build_keycloak:26.6::el9","status":"fixed","packages":[],"package_count":0,"fixed":[],"advisories":["RHSA-2026:95761"],"provider":"redhat-vex","source":"CVE-2026-96447"}],"records":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4375","relation":"upstream","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4375","license":"TLP:CLEAR, mirroring permitted","published_at":"2026-11-05T23:00:00Z","modified_at":"2026-11-11T23:00:00Z","summary":"Keycloak: Mehrere Schwachstellen","details":"Ein Angreifer kann mehrere Schwachstellen in Keycloak ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um einen Denial of Service Angriff durchzuführen und um einen Cross-Site Scripting Angriff durchzuführen.\n\nKeycloak ermöglicht Single Sign-On mit Identity and Access Management für moderne Anwendungen und Dienste.","severity":[{"type":"BSI","score":"mittel","source":"WID-SEC-W-2026-4375"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-4375.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4375"},{"type":"WEB","url":"https://www.keycloak.org/2026/11/keycloak-2682-released"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:95759"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:95760"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:95761"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:96040"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:96039"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:96038"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:96037"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:95762"}]},{"provider":"cvelistv5","source_id":"CVE-2026-96447","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2026-96447","license":"CC-BY-4.0","published_at":"2026-11-06T06:02:51.358Z","modified_at":"2026-11-19T21:36:50.798Z","summary":"Keycloak-services: keycloak-services: stateless token preferred_username fallback enables identity rebinding","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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","source":"CVE-2026-96447"}],"affected":[{"ecosystem":"CVE","package":"Red Hat/Red Hat build of Keycloak 26.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.6.8-2"}]}],"fixed":["26.6.8-2"],"provider":"cvelistv5","source":"CVE-2026-96447","relation":"self"},{"ecosystem":"CVE","package":"Red Hat/Red Hat build of Keycloak 26.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.6-24"}]}],"fixed":["26.6-24"],"provider":"cvelistv5","source":"CVE-2026-96447","relation":"self"},{"ecosystem":"CVE","package":"Red Hat/Red Hat build of Keycloak 26.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"26.6-24"}]}],"fixed":["26.6-24"],"provider":"cvelistv5","source":"CVE-2026-96447","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:95761"},{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:95762"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-96447"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2539288"}]},{"provider":"redhat-vex","source_id":"CVE-2026-96447","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2026-96447","license":"CC-BY-4.0","published_at":"2026-11-05T00:00:00Z","modified_at":"2026-11-17T13:38:33Z","summary":"keycloak-services: keycloak-services: Stateless token preferred_username fallback enables identity rebinding","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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","source":"CVE-2026-96447"},{"type":"Red Hat","score":"Moderate","source":"CVE-2026-96447"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"Red Hat Single Sign-On 7","cpe":"cpe:/a:redhat:red_hat_single_sign_on:7","status":"not_affected","packages":["keycloak-services"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2026-96447"},{"vendor":"Red Hat","product":"Red Hat build of Keycloak 26.6","cpe":"cpe:/a:redhat:build_keycloak:26.6::el9","status":"fixed","packages":["rhbk/keycloak-operator-bundle","rhbk/keycloak-rhel9","rhbk/keycloak-rhel9-operator"],"package_count":3,"fixed":[],"advisories":["RHSA-2026:95762"],"provider":"redhat-vex","source":"CVE-2026-96447"},{"vendor":"Red Hat","product":"Red Hat build of Keycloak 26.6.8","cpe":"cpe:/a:redhat:build_keycloak:26.6::el9","status":"fixed","packages":[],"package_count":0,"fixed":[],"advisories":["RHSA-2026:95761"],"provider":"redhat-vex","source":"CVE-2026-96447"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-96447.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-96447"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2539288"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-96447"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-96447"}]}],"references":[{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:95761"},{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2026:95762"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2026-96447"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2539288"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-96447.json"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2026-96447"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-96447"}],"sources":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2026-4375","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-4375","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-11-11T23:00:00Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2026-96447","url":"https://www.cve.org/CVERecord?id=CVE-2026-96447","license":"CC-BY-4.0","modified_at":"2026-11-19T21:36:50.798Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2026-96447","url":"https://access.redhat.com/security/cve/CVE-2026-96447","license":"CC-BY-4.0","modified_at":"2026-11-17T13:38:33Z","relation":"self"}]}
