Vulnerability Database · npm · keycloak-connect · Version
keycloak-connect 4.4.0
4.4.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 26.1.1.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 05 Sep 2018
Status deprecated release
Licence Apache-2.0
Also known from other sources 2
Newer releases 139
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
keycloak-connect 4.4.0 vulnerabilities
2 vulnerabilities cover keycloak-connect 4.4.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2022-2237: Open Redirect Vulnerability in keycloak-connect | 6.1 medium | 21.0.1 | 02 Mar 2023 |
| CVE-2019-10157: Forced Logout in keycloak-connect | 5.5 medium | 4.8.3 | 13 Jun 2019 |
Looking for another version, or everything Vulert holds for keycloak-connect?
Questions
About keycloak-connect 4.4.0
Is keycloak-connect 4.4.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover keycloak-connect 4.4.0: 0 critical, 0 high, 2 medium and 0 low. The upgrade Vulert recommends is 26.1.1, and each entry above names the fixed version to move to.
Which version of keycloak-connect should I use instead of 4.4.0?
26.1.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 4.4.0 the latest release of keycloak-connect?
No. 4.4.0 was published 05 Sep 2018, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor keycloak-connect for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the keycloak-connect version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.