Skip to main content

8 posts tagged with "upgrades"

View All Tags

Java4Shell (CVE-2026-114938): What Keycloak Operators Need to Do

· 7 min read
Jeff Patzer
Phase Two

Bottom line: if you run Keycloak on x86-64 servers with recent Intel or AMD CPUs, add -XX:-UseBASE64Intrinsics to the JVM today, then move to a patched Java runtime. Java4Shell (CVE-2026-114938), disclosed on November 17, 2026, is a memory-corruption bug in OpenJDK's Base64 decoder, and Keycloak is the first application on the researchers' list of products where they demonstrated remote code execution without authentication, in a default configuration. ARM64 is not affected, which is why Phase Two hosted clusters were never exposed.

Update, November 19, 2026: Red Hat has shipped the patched OpenJDK, the official Keycloak 26.8 images have been refreshed, and every image Phase Two publishes is now on the fixed JDK (21.0.13.1). The tags are listed under the permanent fix.

Keycloak 26.8.2: 33 CVEs and a Critical SAML Bypass

· 8 min read
GR Patil
Phase Two

Bottom line: upgrade now if Keycloak terminates or brokers SAML; within the week otherwise. Keycloak 26.8.2 fixes 33 CVEs. The one that should move your schedule is critical and needs no credentials — a signature bypass in the SAML HTTP-Redirect binding that upstream describes as leading to full account takeover of federated users. The harder problem is that 26 of the 33 have no published advisory yet, so most of this release carries no severity you can plan against.

Keycloak 26.8.1 Released: 19 CVEs, One Unrated SAML Bypass

· 8 min read
GR Patil
Phase Two

Bottom line: upgrade this week if you broker SAML, rely on mTLS token binding, or skip OTP by header; otherwise take it next cycle. Keycloak 26.8.1 fixes 19 CVEs — 18 in Keycloak, all medium or low, plus one high-severity jackson-databind issue. The fix most likely to move your schedule has no CVE — an item filed under Weaknesses that upstream describes as unauthenticated login as an arbitrary user through the SAML broker.

Keycloak 26.7.5: 14 CVEs, and 26.6/26.4 Have No Patch

· 7 min read
GR Patil
Phase Two

Bottom line: upgrade this week if you are on 26.7. If you are on 26.6 or 26.4, the fixes are merged to your branch but nobody has tagged a release, so there is no build to take. Keycloak 26.7.5 fixes 14 CVEs: ten in Keycloak, none rated above medium (6.5), and four in bundled libraries, one of them critical. Three breaking changes, one of which changes what lands in your tokens.

Keycloak LTS: the security backports nobody publishes

· 11 min read
GR Patil
Phase Two

Keycloak publishes releases and container images for the current minor version only. It does backport selected security fixes to the two most recent even-numbered branches, and it tags them — but it cuts no GitHub release and builds no image from those tags. As of today there are nine such tags on release/26.4 and three on release/26.6, containing fixes for CVEs that were announced months ago, that you cannot docker pull from anywhere upstream.

Phase Two now builds them. quay.io/phasetwo/keycloak:26.4.16 and quay.io/phasetwo/keycloak:26.6.7 exist today, built from the tag's own Dockerfile, and we intend to keep building the two previous minor lines alongside the current one for as long as upstream keeps backporting to them.

Keycloak 26.7.4: 6 CVEs, Two Unauthenticated DoS

· 6 min read
GR Patil
Phase Two

Bottom line: upgrade this week if your login page or SAML endpoints are reachable from the internet, or if you run stateless mode on MySQL/MariaDB. Otherwise take it in your normal cycle. Keycloak 26.7.4 fixes six CVEs — five published as high, one medium. Two of them let an unauthenticated attacker exhaust memory and crash the server by hitting endpoints that are open by definition. One breaking change, in Authorization Services URI matching.

Keycloak 26.7.3 Released: 20 CVEs, No Fix for 26.4–26.6

· 7 min read
GR Patil
Phase Two

Bottom line: not an emergency, but upgrade this week if you use token exchange with a Google or Microsoft broker, or FGAP v2 to delegate admin rights. On 26.4, 26.5 or 26.6 there is no patch for you today. Keycloak 26.7.3 fixes 20 CVEs — one high, 17 medium, one low, one unrated — plus two breaking changes. Every one needs a delegated admin account, client credentials, or an intercepted authorization code; the single high is in a test-only dependency.