How severe is CVE-2023-6787?

CVE-2023-6787 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-6787?

CVE-2023-6787 affects the following packages: org.keycloak:keycloak-services (Maven), org.keycloak:keycloak-services (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-6787?

Update org.keycloak:keycloak-services to 22.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6787 is resolved across your whole dependency graph.

How do I detect CVE-2023-6787 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-6787 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2023-6787 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-6787 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-6787?

CVE-2023-6787 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-6787?

CVE-2023-6787 is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-6787 published, and has it been updated?

CVE-2023-6787 was published on April 25, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2023-6787 — keycloak-services

MEDIUM

CVE-2023-6787 is a medium-severity (CVSS 6.5) Improper Authentication vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Keycloak: session hijacking via re-authentication

Also known asGHSA-c9h6-v78w-52wj

Published

Apr 25, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-6787.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Keycloak that occurs from an error in the re-authentication mechanism within org.keycloak.authentication. This flaw allows hijacking an active Keycloak session by triggering a new authentication process with the query parameter "prompt=login," prompting the user to re-enter their credentials. If the user cancels this re-authentication by selecting "Restart login," an account takeover may occur, as the new session, with a different SUB, will possess the same SID as the previous session.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.keycloak:keycloak-services`	all versions	22.0.10`org.keycloak:keycloak-services:22.0.10`
☕Maven	`org.keycloak:keycloak-services`	≥ 23.0.0&&< 24.0.3	24.0.3`org.keycloak:keycloak-services:24.0.3`

Affected Products

2 products · 3 configurations

Application

build of keycloakredhat

all

Application

keycloakredhat

≥ 23.0.0 && < 24.0.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.keycloak:keycloak-services to 22.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-6787 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat build of Keycloak 22	`rhbk/keycloak-operator-bundle:22.0.10-1`	RHSA-2024:1867
Red Hat build of Keycloak 22.0.10	`keycloak-core`	RHSA-2024:1868

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-6787 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

CWE Classification

CWE-287Improper Authentication

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 25, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2023-6787

GHSA-c9h6-v78w-52wj

References

Advisoryaccess.redhat.com · RHSA 2024:1867 Advisoryaccess.redhat.com · RHSA 2024:1868 Advisoryaccess.redhat.com · CVE 2023 6787 Advisorygithub.com · CVE 2023 6787.json Advisorygithub.com · GHSA c9h6 v78w 52wj Advisorynvd.nist.gov · CVE 2023 6787 Reportbugzilla.redhat.com · show bug.cgi Webaccess.redhat.com · package browser Webcatalog.redhat.com · containers Packagegithub.com · keycloak

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting keycloak-services are rated as high or higher (top: critical).

CVE-2026-11800CVE-2026-9083CVE-2026-9800CVE-2026-9705CVE-2026-9086CVE-2026-9799CVE-2026-18963CVE-2026-2092

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-6787 — keycloak-services

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2023-6787 in your dependencies?