medium · CVSS v3 6.4

CVE-2026-107124

CVE-2026-107124 is a flaw in the OIDC logout endpoint of the keycloak-services component in Red Hat Build of Keycloak. The vulnerability all

Overview

CVE-2026-107124 is a flaw in the OIDC logout endpoint of the keycloak-services component in Red Hat Build of Keycloak. The vulnerability allows an attacker to set a session cookie based on an unvalidated token hint before security checks, enabling session fixation and hijacking. It can lead to full account takeover for authenticated users.

Description

A flaw was found in the OIDC logout endpoint of the keycloak-services component, which handles user session termination in Red Hat Build of Keycloak. The issue occurs because the system sets a session cookie based on an unvalidated token hint before completing security checks. An attacker can use this flaw to fix a session ID in a victim's browser, allowing them to hijack the victim's subsequent login and gain full control over their account.

Impact

Confidentiality: compromised account data; Integrity: attacker can modify session state; Availability: not directly impacted. Users with active sessions are at risk of hijacking. Defenders must monitor session anomalies.

Remediation

Apply the latest Keycloak patch that validates token hints before setting session cookies. If patch unavailable, disable the OIDC logout endpoint or enforce strict token validation. Additionally, implement session fixation protection and monitor for abnormal session cookie patterns.

Risk context

Severity is medium (CVSS 6.4). No EPSS data. The vulnerability is exploitable in production environments with OIDC logout enabled, so timely patching is recommended.

Affected products

  • Red Hat Keycloak
  • Keycloak Services
  • Keycloak OIDC logout
  • Red Hat Build of Keycloak

Scores

Severity
medium
CVSS v2
6.6
CVSS v3
6.4
CVSS v4
—
EPSS
—

Keycloak OIDC Session Fixation Account Hijack Red Hat Authentication Security Patch

← All CVEs

Related CVEs

medium

CVE-2026-114427

The GutenKit WordPress plugin before 2.5.5 does not properly sanitize custom CSS saved against a post before printing it inside an inline style block on the published page, allowing users with the Author role and above to break out of the style element and store JavaScript that executes in the browser of any visitor who views the post. Exploitation affects sites running WordPress below 7.0.

View analysis

medium

CVE-2026-120659

The Redirection for Contact Form 7 plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.2.14 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to write arbitrary post meta values to newly created lead posts and copy arbitrary server-side files with allowed MIME-type extensions into the plugin's uploads directory. Exploitation requires a published Contact Form 7 form configured with the Save Entry (Save Lead) action enabled on the target site.

View analysis

medium

CVE-2026-123287

In JetBrains Datalore before 2026.4 private notebook files could be downloaded without authentication via published interactive reports

View analysis

medium

CVE-2026-84164

The HTML report that plist-to-html, CodeChecker parse --export html and CodeChecker cmd diff --output html generate puts the report message, the checker name and the source file path into a script block through json.dumps. json.dumps does not escape the less-than character, so a closing script tag in any of those three fields ends the script element and what follows is parsed as HTML. The input author is whoever controls the analysed tree or a third-party result file that report-converter ingests, or who holds PRODUCT_STORE in the cmd diff flow. The viewer is somebody else: docs/jenkins_gerrit_integration.md documents writing the report into Jenkins userContent and posting its URL into a Gerrit review. One caveat worth stating up front is that Jenkins serves userContent under a restrictive CSP that would block an inline handler, so that destination is probably safe as configured. The generated report sets no CSP of its own, so the impact lands wherever it is published without one.

View analysis