Keycloak Cluster on Three VMs: Engineers Detail Embedded Infinispan Setup, HA Testing Failures, and Bug Fix
A project required centralized authentication and authorization for 25,000–30,000 active users distributed nationwide, demanding strong scalability and reliability. The team selected Keycloak and rejected a single instance because it could not meet throughput or SLA targets. They therefore built a three-node cluster on isolated virtual machines using Embedded Infinispan and JGroups.
Kubernetes was considered excessive for the environment. The chosen architecture placed each Keycloak node in a separate data center, shared a PostgreSQL database clustered with Patroni, and enabled cache mode ispn so sessions replicate across nodes. TCP ports 7800 and 57800 were opened between the VMs for Infinispan communication and failure detection.
Each node registers its address in the JGROUPS_PING table at startup, allowing dynamic membership without static TCPPING lists. The JVM flag -Djgroups.external_addr and explicit node-name entries in cache-ispn.xml ensured correct visibility of external IPs and hostnames across data centers.
Failover tests included node restarts, database connectivity loss, and complete data-center isolation. When only Keycloak nodes lost connectivity while the database remained reachable, the cluster recovered automatically. Full data-center outages, however, produced split-brain states, multiple coordinators, and persistent 5xx errors. The built-in healthcheck did not detect the condition even after an upgrade that added cluster-specific checks.
A temporary Python watcher was deployed beside each container. It polled health endpoints and the JGROUPS_PING table, restarting any node that appeared as an extra coordinator. The root cause was reported in GitHub issue 45980; Keycloak developers acknowledged the bug and shipped a fix. After verification on test and staging environments, the production cluster was updated and now tolerates single data-center failure without session loss.
Related articles
Critical PHP Vulnerability to Receive Patch on November 19 at 23:00 JST
A critical-severity vulnerability has been identified in the PHP scripting language, affecting all supported branches. The PHP security team has pre-announced a security update release scheduled for 14:00-14:30 UTC on November 19, which corresponds to 23:00-23:30 Japan Standard Time. Although the maximum severity rating is critical, the flaw does not impact default configurations and requires uncommon system setups to be exploitable. No specific technical details, CVE identifiers, or attack vectors have been disclosed ahead of the patch. The update forms part of PHP's regular four-week release cycle. This follows another serious PHP flaw called PHP2Shell that required emergency remediation in October. Organizations are strongly advised to prepare for immediate deployment once the fix becomes available.
Java4Shell Vulnerability Enables Remote Code Execution Without Authentication Across Keycloak, Jira, Confluence and Other Enterprise Platforms
A critical flaw tracked as CVE-2026-114938 and dubbed Java4Shell allows unauthenticated remote code execution on multiple widely deployed Java applications including Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate when running in their default configurations. The root cause lies in a buffer overflow inside the AVX-512-accelerated Base64 decoder of HotSpot JVM on x86-64 processors that support the VBMI instruction set. Malformed Base64 strings ending with an extra equals sign cause the decoder to write 62 or 63 bytes past the allocated output buffer before the Java runtime rejects the input. Because several authentication-related components such as Basic Auth headers, SAML artifacts and CSRF tokens are decoded before any session or access-control checks occur, the vulnerable code path executes with attacker-controlled data prior to authentication. The issue affects Java 17.0.6 and later releases on lines 21, 25 and 27 when running on Intel Xeon Ice Lake or newer and AMD Zen 4 CPUs; ARM64 systems remain unaffected. Oracle and OpenJDK released fixes on 18 November, CISA issued an urgent advisory the same day, and Amazon has already updated Corretto builds while Red Hat continues work on its distributions.
Attackers Exploit Critical Apache Roller Flaw CVE-2026-129448 for Unauthenticated Remote Code Execution
Cybercriminals are actively exploiting a critical vulnerability in Apache Roller that allows remote code execution on the server without any credentials. The Java-based blogging platform received CVE-2026-129448 with a CVSS score of 9.8, and the Apache Software Foundation has confirmed active exploitation in the wild. The attack path targets the XML-RPC endpoint, which accepts vendor extension types and deserializes requests before performing authentication. The flaw affects versions 4.0.0 through 6.1.4, expanding the scope beyond the earlier CVE-2026-82384 that only listed version 6.1.5 as affected. Disabling XML-RPC through the admin interface provides no protection on older versions because deserialization occurs before the setting is checked. The recommended fix is upgrading to version 6.1.6 or later, which properly disables extension types and enforces the configuration. Organizations unable to update immediately should set enabledForExtensions to false in web.xml or remove the XML-RPC servlet mapping.
PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update
The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.