CVE-2019-3868

What it is

Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user’s browser session.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. Limited direct impact.

Exploit odds

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

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2019-04-24 16:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:35 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 3.8 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2019-04-24 16:29 UTC

Last modified

2026-06-17 02:35 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-200 · Information exposure

Record status

Modified

Affected

• Redhat Keycloak ≤ 6.0.0

Attack profile CVSS 3.0 · 3.8

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

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-2019-3868.md and follow it. Check whether this project is affected by CVE-2019-3868. 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