CVE-2025-12390: Org.keycloak.protocol.oidc.endpoints.logoutendpoint: offline session takeover due to reused authentication session id
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
- Fixed version: Keycloak keycloak 26.0.0.
Low priority for now. Upgrade to Keycloak keycloak 26.0.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 28, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-384
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · redhat
- 6.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Keycloak keycloak
- before 26.0.0affected · semver
Red Hat Red Hat build of Keycloak 26.2
- 26.2.11-1 and laternot affected · rpm
- 26.2-12 and laternot affected · rpm
- 26.2-12 and laternot affected · rpm
Red Hat Red Hat build of Keycloak 26.2.11
- all versionsunknown
Red Hat Red Hat build of Keycloak 26.4
- 26.4.4-1 and laternot affected · rpm
- 26.4-3 and laternot affected · rpm
- 26.4-3 and laternot affected · rpm
Red Hat Red Hat build of Keycloak 26.4.4
- all versionsunknown
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.keycloak:keycloak-services | before 26.0.0 | 26.0.0 |
Same product
keycloak: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-12161It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset…35Monitor
- CVE-2014-3709The org.keycloak.services.resources.SocialResource.callback method in JBoss KeyCloak before 1.0.3.Final allows remote attackers to conduct…35Monitor
- CVE-2017-12159It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-12110Oct 23, 2025 · Keycloak: org.keycloak:keycloak-services: user can refresh offline session even after client's offline_access scope was removed21Monitor
- ← EarlierCVE-2025-10939Oct 28, 2025 · Org.keycloak/keycloak-quarkus-server: unable to restrict access to the admin console14Monitor
- Later →CVE-2025-11538Nov 13, 2025 · Keycloak-server: debug default bind address27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Keycloak keycloak | 26.0.0 | Vendor (CNA) |
| Maven:org.keycloak:keycloak-services | 26.0.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-384 · Session FixationCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session Credential Falsification through ForgingCAPEC-196likelihood: Medium · Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Accessing/Intercepting/Modifying HTTP CookiesCAPEC-31likelihood: High · High
- Manipulating Opaque Client-based Data TokensCAPEC-39likelihood: High · Medium
- Session Credential Falsification through PredictionCAPEC-59likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
- Session FixationCAPEC-61likelihood: Medium · High
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Access Token Manipulation: Create Process with TokenT1134.002
- Access Token Manipulation: Make and Impersonate TokenT1134.003
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Forge Web CredentialsT1606
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.