VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

keycloak: vulnerability history, versions and safety

keycloak is a package in the Bitnami ecosystem. Vulert records 69 vulnerabilities for it across 21 affected ranges, first recorded in Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
69 vulnerabilities recorded C3 H25 M36 L5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
69 in the last 12 months

Most recent disclosure 31 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all keycloak vulnerabilities

Vulert verdict on keycloak i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 31 Aug 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 69 vulnerabilities on record across 1 year, 69 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 69 over 1 year · 69 in the last year i
  • Latest disclosure 31 Aug 2026 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 26.7.3 (exclusive) 17
up to 26.7.2 (exclusive) 5
from 26.6.0 up to 26.6.5 (exclusive) 2
from 26.6.0 up to 26.6.4 (exclusive) 1
from 26.5.2 up to 26.5.3 (exclusive) 1
from 26.4.0 up to 26.4.14 (exclusive) 8
from 26.4.0 up to 26.4.13 (exclusive) 6
from 26.4.0 up to 26.4.12 (exclusive) 8
up to 26.4.12 (exclusive) 1
from 26.4.0 up to 26.4.11 (exclusive) 2
from 26.4.0 up to 26.4.10 (exclusive) 1
up to 26.4.9 (exclusive) 1
up to 26.4.4 (exclusive) 1
from 26.4.0 up to 26.4.1 (exclusive) 2
from 26.2.0 up to 26.2.14 (exclusive) 2
from 26.2.0 up to 26.2.1 (exclusive) 6
from 26.0.0 up to 26.0.11 (exclusive) 1
up to 24.0.7 (exclusive) 1
from 22.0.0 up to 24.0.7 (exclusive) 1
from 22.0.0 up to 22.12.0 (exclusive) 1
from 22.0.0 up to 22.0.12 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 69

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

03 Vulnerabilities

Recorded vulnerabilities for keycloak

The 5 most severe of 69 vulnerabilities recorded for this package

Search all 69 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-18573: Keycloak Client Access-Type Policy Bypass Vulnerability N/A medium 26.7.3 31 Aug 2026
CVE-2026-16105: Keycloak Package Vulnerability Due to Missing Per-Role Authorization on Composite Endpoints N/A medium 26.7.3 31 Aug 2026
CVE-2026-16104: Keycloak Package Exposes Sensitive reCAPTCHA Secrets to View-Only Admins N/A medium 26.7.3 31 Aug 2026
CVE-2026-16093: Keycloak Package Vulnerability - Unsigned JWT Assertion Bypass N/A medium 26.7.3 31 Aug 2026
CVE-2026-16089: Keycloak Package Vulnerability - Authorization Codes Retargeting Risk N/A medium 26.7.3 31 Aug 2026

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

Is keycloak safe to use?

Vulert records 69 vulnerabilities for keycloak in Bitnami: 3 critical, 25 high, 36 medium and 5 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does keycloak have?

69 vulnerabilities are recorded for keycloak in the Bitnami ecosystem: 3 critical, 25 high, 36 medium and 5 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new keycloak vulnerabilities disclosed?

69 vulnerabilities were recorded for keycloak in the last 12 months, and the oldest entry in this database dates to 25 Aug 2026. 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 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 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the keycloak version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.