NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2023-6291 — keycloak-services

HIGHFix: keycloak/keycloak@b2e9110

CVE-2023-6291 is a high-severity (CVSS 7.1) Open Redirect vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Keycloak: redirect_uri validation bypass

Also known asGHSA-mpwq-j3xf-7m5w
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 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-6291.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk
0.00%0.48%0.97%1.45%0.2%0.9%May 26Sep 26Nov 26

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

1 pkg affected
☕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

An issue was found in the redirect_uri validation logic that allows for a bypass of otherwise explicitly allowed hosts.

The problem arises in the verifyRedirectUri method, which attempts to enforce rules on user-controllable input, but essentially causes a desynchronization in how Keycloak and browsers interpret URLs. Keycloak, for example, receives "www%2ekeycloak%2eorg%2fapp%2f:[email protected]" and thinks the authority to be keycloak.org when it is actually example.com. This happens because the validation logic is performed on a URL decoded version, which no longer represents the original input.

Acknowledgements

Karel Knibbe

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-servicesall versions23.0.3org.keycloak:keycloak-services:23.0.3

Affected Products

7 products · 13 configurations
Application
keycloakredhat
< 22.0.7
range
Application
migration toolkit for applicationsredhat
2 versions
6.07.0
Application
openshift container platformredhat
2 versions
4.114.12
Application
openshift container platform for ibm zredhat
2 versions
4.94.10
Application
openshift container platform for linuxoneredhat
2 versions
4.94.10
Application
openshift container platform for powerredhat
2 versions
4.94.10

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

  3. Workarounds

    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

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 HatImportant
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2023-6291 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Keycloak 22rhbk/keycloak-operator-bundle:22.0.7-1RHSA-2023:7861
Red Hat build of Keycloak 22.0.7see advisoryRHSA-2023:7860
Red Hat Single Sign-On 7rh-sso7-keycloakRHSA-2024:0804
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.11-2.redhat_00003.1.el7ssoRHSA-2023:7854
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.12-1.redhat_00001.1.el7ssoRHSA-2024:0798
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.11-2.redhat_00003.1.el8ssoRHSA-2023:7856
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.12-1.redhat_00001.1.el8ssoRHSA-2024:0799
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.11-2.redhat_00003.1.el9ssoRHSA-2023:7855

Frequently Asked Questions

An issue was found in the redirect_uri validation logic that allows for a bypass of otherwise explicitly allowed hosts. The problem arises in the verifyRedirectUri method, which attempts to enforce rules on user-controllable input, but essentially causes a desynchronization in how Keycloak and browsers interpret URLs. Keycloak, for example, receives "[www%2ekeycloak%2eorg%2fapp%2f:[email protected]](https://www%2ekeycloak%2eorg%2fapp%2f:[email protected]/)" and thinks the authority to be keycloak.org when it is actually example.com. This happens because the validation logic is performed on a URL deco
O3 Security · Impact-Aware SCA

Is CVE-2023-6291 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2023-6291: keycloak-services — Fixed in 23.0.3