CVE-2022-2237: Open Redirect Vulnerability in keycloak-connect

keycloak-connect Updated 02 Oct 2025

Summary

02/03/2023
Yes i
Moderate
6.1

CVE-2022-2237: keycloak-connect contains Open redirect vulnerability in the Node.js adapter. Affects keycloak-connect versions < 21.0.1. Fixed in 21.0.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

keycloak-connect is an npm package that provides a Node.js adapter for integrating applications with Keycloak, an open-source identity and access management solution. It allows developers to secure their applications by handling authentication and authorization. However, a vulnerability has been discovered in the Node.js adapter of keycloak-connect that could potentially lead to an open redirect attack.

Vulnerability Detail

The vulnerability exists when forwarding requests to Keycloak using the checkSSO function with the query parameter prompt=none. This allows an attacker to manipulate the redirect URL and trick users into visiting malicious websites. By exploiting this vulnerability, an attacker could potentially steal sensitive information, perform phishing attacks, or redirect users to malicious content.

How To Fix

Latest published version: 26.1.1 as of 22 Oct 2026

npm install keycloak-connect@26.1.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

21.0.1

This is the first release that contains the fix.

npm install keycloak-connect@21.0.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to update the keycloak-connect package to the latest version as soon as possible.

Conclusion

The open redirect vulnerability in keycloak-connect can have serious security implications, potentially leading to the compromise of user information or the execution of malicious actions. It is crucial for developers to update their keycloak-connect package to the latest version to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for keycloak-connect →

Share this vulnerability

FAQ

keycloak-connect is an npm package that provides a Node.js adapter for integrating applications with Keycloak, an open-source identity and access management solution.

An open redirect vulnerability occurs when a web application allows an attacker to redirect users to external websites without proper validation. This can be exploited to trick users into visiting malicious websites or phishing pages.

By manipulating the redirect URL in requests to Keycloak using the checkSSO function with the prompt=none query parameter, an attacker can redirect users to malicious websites or phishing pages.

This vulnerability could lead to sensitive information being stolen, users being tricked into visiting malicious websites, or being redirected to phishing pages where their credentials could be compromised.

Yes, developers should update their keycloak-connect package to version 21.0.1 or later to fix this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for keycloak-connect.

How To Fix

Latest published version: 26.1.1 as of 22 Oct 2026

npm install keycloak-connect@26.1.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

21.0.1

This is the first release that contains the fix.

npm install keycloak-connect@21.0.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback