keycloak-connect and keycloak-js improperly handle invalid tokens
It was found that the Keycloak Node.js adapter 2.5 - 3.0 did not handle invalid tokens correctly. An attacker could use this flaw to bypass authentication and gain access to restricted information, or to possibly conduct further attacks.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | keycloak-connect | >= 2.5.0, < 3.1.0 | 3.1.0 |
| npm package | keycloak-js | >= 2.5.0, < 3.1.0 | 3.1.0 |
References
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H- Weakness (CWE)
CWE-253- Platform
- npm
- Package
keycloak-connect, keycloak-js- Disclosed
- 15.11.2017
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-mw35-24gh-f82w - CC BY 4.0
Vulnerability history: keycloak-connect
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 3
- First → latest
- 11.2017 03.2023
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- Medium 2
Disclosures per year
- 2017: 1
- 2018: 0
- 2019: 1
- 2020: 0
- 2021: 0
- 2022: 0
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 0
-
keycloak-connect and keycloak-js improperly handle invalid tokens this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.