CVE-2025-12390

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2025-10-28 14:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-18 21:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 6.0 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2025-10-28 14:15 UTC

Last modified

2026-10-18 21:10 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-384

Record status

Deferred

Attack profile CVSS 3.1 · 6.0

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-12390.md and follow it. Check whether this project is affected by CVE-2025-12390. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge