Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2017-7474 — keycloak-connect

CRITICAL

CVE-2017-7474 is a critical-severity (CVSS 9.8) CWE-253 vulnerability in keycloak-connect. A fix is available for keycloak-connect — see the affected versions and patch details below.

keycloak-connect and keycloak-js improperly handle invalid tokens

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk
1.23%1.83%2.44%3.04%1.7%2.5%Apr 26Aug 26Oct 26

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

How urgent is this, really

CVE-2017-7474 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 388,997 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

157other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
keycloak-connectnpm
112Kdownloads / week
keycloak-jsnpm
1.1Mdownloads / week

Description

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 Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmkeycloak-connect≥ 2.5.0&&< 3.1.03.1.0npm install keycloak-connect@3.1.0
📦npmkeycloak-js≥ 2.5.0&&< 3.1.03.1.0npm install keycloak-js@3.1.0

Affected Products

1 product · 11 configurations
Application
keycloak-nodejs-auth-utilskeycloak
9 versions
2.5.02.5.12.5.22.5.32.5.42.5.52.5.62.5.73.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update keycloak-connect to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7474 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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
RHSA-2017:1203Red Hat Single Sign-On 7.1

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2017-7474 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2017-7474: keycloak-connect — Fixed in 3.1.0