Threats Tagged 'cve-2025-12390'
View all threats tagged with 'cve-2025-12390'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2025-12390'
Click on any threat for detailed analysis and mitigation recommendations
Red Hat build of Keycloak is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat build of Keycloak for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services. Red Hat build of Keycloak Operator for OpenShift simplifies deployment and management of Keycloak 26.2.11 clusters. This erratum releases new images for Red Hat build of Keycloak 26.2.11 for use within the OpenShift Container Platform cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release. Security fixes: * Deserialization of Untrusted Data in LDAP User Federation (CVE-2025-13467) Join the discussion | GCVE Database | 11/25/2025, 16:12:38 UTC Added: 06/24/2026, 16:59:27 UTC |
Red Hat build of Keycloak 26.2.11 is a standalone server, based on the Keycloak project, that provides authentication and standards-based single sign-on capabilities for web and mobile applications. Security fixes: * Deserialization of Untrusted Data in LDAP User Federation (CVE-2025-13467) Join the discussion | GCVE Database | 11/25/2025, 16:06:13 UTC Added: 06/24/2026, 16:59:27 UTC |
Red Hat build of Keycloak is an integrated sign-on solution, available as a Red Hat JBoss Middleware for OpenShift containerized image. The Red Hat build of Keycloak for OpenShift image provides an authentication server that you can use to log in centrally, log out, and register. You can also manage user accounts for web applications, mobile applications, and RESTful web services. Red Hat build of Keycloak Operator for OpenShift simplifies deployment and management of Keycloak 26.4.4 clusters. This erratum releases new images for Red Hat build of Keycloak 26.4.4 for use within the OpenShift Container Platform cloud computing Platform-as-a-Service (PaaS) for on-premise or private cloud deployments, aligning with the standalone product release. Security fixes: * Unable to restrict access to the admin console (CVE-2025-10939) * Debug default bind address (CVE-2025-11538) * User can refresh offline session even after client's offline_access scope was removed (CVE-2025-12110) * WebAuthn Attestation Statement Verification Bypass (CVE-2025-12150) * Offline Session takeover due to reused Authentication Session ID (CVE-2025-12390) Join the discussion | GCVE Database | 11/13/2025, 19:30:13 UTC Added: 06/24/2026, 16:59:27 UTC |
Red Hat build of Keycloak 26.4.4 is a standalone server, based on the Keycloak project, that provides authentication and standards-based single sign-on capabilities for web and mobile applications. Security fixes: * Unable to restrict access to the admin console (CVE-2025-10939) * Debug default bind address (CVE-2025-11538) * User can refresh offline session even after client's offline_access scope was removed (CVE-2025-12110) * WebAuthn Attestation Statement Verification Bypass (CVE-2025-12150) * Offline Session takeover due to reused Authentication Session ID (CVE-2025-12390) Join the discussion | GCVE Database | 11/13/2025, 17:51:13 UTC Added: 06/24/2026, 16:59:28 UTC |
A flaw was found in Keycloak. In Keycloak where a user can accidentally get access to another user's session if both use the same device and browser. This happens because Keycloak sometimes reuses session identifiers and doesn’t clean up properly during logout when browser cookies are missing. As a result, one user may receive tokens that belong to another user. Join the discussion | CVE Database V5 | 10/28/2025, 13:23:34 UTC Added: 10/28/2025, 13:42:02 UTC |
Showing 1 to 5 of 5 results