VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

keycloak-connect: vulnerability history, versions and safety

keycloak-connect is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 78 releases, from Nov 2017 to Mar 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all keycloak-connect vulnerabilities

Vulert verdict on keycloak-connect 26.1.1 i

Updated on 23 Oct 2026

Good news: 26.1.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 70/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Stay on 26.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 26.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 26.1.1 — unaffected i
  • Vulnerabilities on record 3 over 5 years · 0 in the last year i
  • Latest disclosure 02 Mar 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 14 packages i
  • Stars 740 i
  • OpenSSF scorecard 4/10 i
  • Last release 20 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for keycloak-connect, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
26.1.1 28 Jan 2025 none Apache-2.0 — Details →
26.1.0 15 Jan 2025 none Apache-2.0 — Details →
26.0.8 13 Jan 2025 none Apache-2.0 — Details →
26.0.7 03 Dec 2024 none Apache-2.0 — Details →
26.0.6 22 Nov 2024 none Apache-2.0 — Details →
26.0.5 01 Nov 2024 none Apache-2.0 — Details →
26.0.4 30 Oct 2024 none Apache-2.0 — Details →
26.0.2 24 Oct 2024 none Apache-2.0 — Details →
26.0.1 17 Oct 2024 none Apache-2.0 — Details →
26.0.0 04 Oct 2024 none Apache-2.0 — Details →
25.0.6 19 Sep 2024 none Apache-2.0 — Details →
25.0.5 10 Sep 2024 none Apache-2.0 — Details →
25.0.4 19 Aug 2024 none Apache-2.0 — Details →
25.0.3 19 Aug 2024 none Apache-2.0 — Details →
25.0.2 18 Jul 2024 none Apache-2.0 — Details →
25.0.1 20 Jun 2024 none Apache-2.0 — Details →
25.0.0 10 Jun 2024 none Apache-2.0 — Details →
24.0.5 04 Jun 2024 none Apache-2.0 — Details →
24.0.4 08 May 2024 none Apache-2.0 — Details →
24.0.3 16 Apr 2024 none Apache-2.0 — Details →
24.0.2 24 Mar 2024 none Apache-2.0 — Details →
24.0.1 05 Mar 2024 none Apache-2.0 — Details →
24.0.0 04 Mar 2024 none Apache-2.0 — Details →
23.0.7 22 Feb 2024 none Apache-2.0 — Details →
23.0.6 02 Feb 2024 none Apache-2.0 — Details →
23.0.5 29 Jan 2024 none Apache-2.0 — Details →
23.0.4 08 Jan 2024 none Apache-2.0 — Details →
23.0.3 15 Dec 2023 none Apache-2.0 — Details →
23.0.2 14 Dec 2023 none Apache-2.0 — Details →
23.0.1 29 Nov 2023 none Apache-2.0 — Details →
23.0.0 23 Nov 2023 none Apache-2.0 — Details →
22.0.5 24 Oct 2023 none Apache-2.0 — Details →
22.0.4 04 Oct 2023 none Apache-2.0 — Details →
22.0.3 12 Sep 2023 none Apache-2.0 — Details →
22.0.2 11 Sep 2023 none Apache-2.0 — Details →
22.0.1 18 Jul 2023 none Apache-2.0 — Details →
22.0.0 11 Jul 2023 none Apache-2.0 — Details →
21.1.2 28 Jun 2023 none Apache-2.0 — Details →
21.1.1 26 Apr 2023 none Apache-2.0 — Details →
21.1.0 19 Apr 2023 none Apache-2.0 — Details →
21.0.2 30 Mar 2023 none Apache-2.0 — Details →
21.0.1 01 Mar 2023 none Apache-2.0 — Details →
21.0.0 23 Feb 2023 M1 Apache-2.0 Yes Details →
20.0.5 21 Feb 2023 M1 Apache-2.0 Yes Details →
20.0.3 12 Jan 2023 M1 Apache-2.0 Yes Details →
20.0.2 13 Dec 2022 M1 Apache-2.0 Yes Details →
20.0.1 07 Nov 2022 M1 Apache-2.0 Yes Details →
20.0.0 01 Nov 2022 M1 Apache-2.0 Yes Details →
19.0.3 06 Oct 2022 M1 Apache-2.0 Yes Details →
19.0.2 14 Sep 2022 M1 Apache-2.0 Yes Details →
19.0.1 29 Jul 2022 M1 Apache-2.0 Yes Details →
19.0.0 27 Jul 2022 M1 Apache-2.0 Yes Details →
18.0.2 24 Jun 2022 M1 Apache-2.0 Yes Details →
18.0.1 16 Jun 2022 M1 Apache-2.0 Yes Details →
18.0.0 20 Apr 2022 M1 Apache-2.0 Yes Details →
17.0.1 23 Mar 2022 M1 Apache-2.0 Yes Details →
17.0.0 10 Feb 2022 M1 Apache-2.0 Yes Details →
16.1.1 25 Jan 2022 M1 Apache-2.0 Yes Details →
16.1.0 20 Dec 2021 M1 Apache-2.0 Yes Details →
16.0.0 17 Dec 2021 M1 Apache-2.0 Yes Details →
15.1.1 17 Dec 2021 M1 Apache-2.0 Yes Details →
15.1.0 10 Dec 2021 M1 Apache-2.0 Yes Details →
15.0.2 20 Aug 2021 M1 Apache-2.0 Yes Details →
15.0.1 06 Aug 2021 M1 Apache-2.0 Yes Details →
15.0.0 30 Jul 2021 M1 Apache-2.0 Yes Details →
14.0.0 18 Jun 2021 M1 Apache-2.0 Yes Details →
13.0.1 25 May 2021 M1 Apache-2.0 Yes Details →
13.0.0 06 May 2021 M1 Apache-2.0 Yes Details →
12.0.4 01 Mar 2021 M1 Apache-2.0 Yes Details →
12.0.3 16 Feb 2021 M1 Apache-2.0 Yes Details →
12.0.2 19 Jan 2021 M1 Apache-2.0 Yes Details →
12.0.1 18 Dec 2020 M1 Apache-2.0 Yes Details →
12.0.0 16 Dec 2020 M1 Apache-2.0 Yes Details →
11.0.3 05 Nov 2020 M1 Apache-2.0 Yes Details →
11.0.2 31 Aug 2020 M1 Apache-2.0 Yes Details →
11.0.1 21 Aug 2020 M1 Apache-2.0 Yes Details →
11.0.0 22 Jul 2020 M1 Apache-2.0 Yes Details →
10.0.2 02 Jun 2020 M1 Apache-2.0 Yes Details →
10.0.1 08 May 2020 M1 Apache-2.0 Yes Details →
10.0.0 29 Apr 2020 M1 Apache-2.0 Yes Details →
9.0.3 14 Apr 2020 M1 Apache-2.0 Yes Details →
9.0.2 24 Mar 2020 M1 Apache-2.0 Yes Details →
9.0.0 17 Feb 2020 M1 Apache-2.0 Yes Details →
8.0.2 05 Feb 2020 M1 Apache-2.0 Yes Details →
8.0.1 02 Dec 2019 M1 Apache-2.0 Yes Details →
8.0.0 15 Nov 2019 M1 Apache-2.0 Yes Details →
7.0.1 16 Oct 2019 M1 Apache-2.0 Yes Details →
7.0.0 24 Aug 2019 M1 Apache-2.0 Yes Details →
6.0.1 24 Apr 2019 M1 Apache-2.0 Yes Details →
6.0.0 17 Apr 2019 M1 Apache-2.0 Yes Details →
5.0.0 06 Mar 2019 M1 Apache-2.0 Yes Details →
4.8.3 15 Jan 2019 M1 Apache-2.0 Yes Details →
4.8.2 03 Jan 2019 M2 Apache-2.0 Yes Details →
4.8.1 19 Dec 2018 M2 Apache-2.0 Yes Details →
4.8.0 17 Dec 2018 M2 Apache-2.0 Yes Details →
4.7.0 04 Dec 2018 M2 Apache-2.0 Yes Details →
4.6.0 14 Nov 2018 M2 Apache-2.0 Yes Details →
4.5.0 26 Sep 2018 M2 Apache-2.0 Yes Details →
4.4.0 05 Sep 2018 M2 Apache-2.0 Yes Details →
4.3.0 15 Aug 2018 M2 Apache-2.0 Yes Details →
4.2.1 03 Aug 2018 M2 — Yes Details →
4.2.0 01 Aug 2018 M2 — Yes Details →
4.1.0 04 Jul 2018 M2 — Yes Details →
4.0.0 13 Jun 2018 M2 — Yes Details →
4.0.0-beta.3 24 May 2018 M2 — Yes Details →
4.0.0-beta.2 02 May 2018 M2 — Yes Details →
4.0.0-beta.1 22 Mar 2018 M2 — Yes Details →
3.4.3 04 Jan 2018 M2 — Yes Details →
3.4.2 21 Dec 2017 M2 — Yes Details →
3.4.1 08 Dec 2017 M2 — Yes Details →
3.4.1-cr.1 30 Nov 2017 M2 — Yes Details →
3.4.0 10 Nov 2017 M2 — Yes Details →
3.4.0-cr.1 08 Nov 2017 M2 — Yes Details →
3.3.0 26 Oct 2017 M2 — Yes Details →
3.3.0-cr.2 12 Sep 2017 M2 — Yes Details →
3.3.0-cr.1 28 Aug 2017 M2 — Yes Details →
3.2.1 21 Jul 2017 M2 — Yes Details →
3.2.0 05 Jul 2017 M2 — Yes Details →
3.2.0-cr.1 30 Jun 2017 M2 — Yes Details →
3.1.0 03 May 2017 M2 — Yes Details →

The newest 120 of 139 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2019 1
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for keycloak-connect

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-7474: Vulnerability in keycloak-connect and keycloak-js 9.8 critical 3.1.0 15 Nov 2017
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

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About keycloak-connect

Is keycloak-connect safe to use?

Vulert records 3 vulnerabilities for keycloak-connect in npm: 1 critical, 0 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is keycloak-connect's Vulert package health score?

Vulert scores keycloak-connect 70/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of keycloak-connect affected?

No. 26.1.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of keycloak-connect should I use?

26.1.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does keycloak-connect have?

3 vulnerabilities are recorded for keycloak-connect in the npm ecosystem: 1 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new keycloak-connect vulnerabilities disclosed?

0 vulnerabilities were recorded for keycloak-connect in the last 12 months, and the oldest entry in this database dates to 15 Nov 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of keycloak-connect are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.