Skip to content

chore: prepare keycloak v26.8.1 release - #152

Merged
mikkeldamsgaard merged 1 commit into
mainfrom
release/keycloak-26.8.1
Oct 20, 2026
Merged

mikkeldamsgaard merged 1 commit into
mainfrom
release/keycloak-26.8.1

Conversation

@mikkeldamsgaard

Copy link
Copy Markdown
Contributor

Release keycloak 26.8.1 — the chart version syncs with the upstream Keycloak appVersion, bumped on main via #150.

  • Security: Keycloak 26.7.4 → 26.8.1 — ~20 CVE fixes, notably CVE-2026-94000 (manage-users → realm-admin escalation), CVE-2026-94218 (2FA bypass), CVE-2026-96446 (PAR single-use bypass), and CVE-2026-97846 (token-exchange mTLS binding bypass).
  • Changed (upstream 26.8.0): login failures are now persisted in the DB, so the first start against an existing database runs a schema migration plus non-blocking background index creation. None of the KC_* options this chart sets were removed or renamed.

Merging this triggers the release workflow (GHCR OCI push, keycloak-26.8.1 tag, GitHub release).

How to verify

helm lint charts/keycloak      # clean
helm unittest charts/keycloak  # 103 tests passing
make e2e-keycloak              # dev / postgres / replicas all passed on 26.8.1 (#150, locally and in CI)

🤖 Generated with Claude Code

Sync chart version with upstream appVersion 26.8.1 (bumped on main via
#150). Security: ~20 upstream CVE fixes in 26.8.1. Keycloak 26.8
persists login failures in the DB (first-boot schema migration).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mikkeldamsgaard
mikkeldamsgaard merged commit 08bef3c into main Oct 20, 2026
14 checks passed
@mikkeldamsgaard
mikkeldamsgaard deleted the release/keycloak-26.8.1 branch October 20, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant