From 8c7ba56a8e9ba98b674b9c809f9e3590d5e5bb6a Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Thu, 19 Nov 2026 15:46:26 +0000 Subject: [PATCH 1/6] docs: add 0.26.0 release blog post Covers the headline features (automatic TLS certificate rotation, configurable PQC key exchange, client address visibility for filters, per-gateway PROXY protocol configuration, new ppc64le/s390x container images) and calls out that the 0.26.0 container images pick up the critical OpenJDK fix from RHSA-2026:100567. Assisted-by: Claude Sonnet 5 Signed-off-by: Keith Wall --- _posts/2026-11-19-release-0_26_0.md | 90 +++++++++++++++++++++++++++++ 1 file changed, 90 insertions(+) create mode 100644 _posts/2026-11-19-release-0_26_0.md diff --git a/_posts/2026-11-19-release-0_26_0.md b/_posts/2026-11-19-release-0_26_0.md new file mode 100644 index 00000000..5191a2f1 --- /dev/null +++ b/_posts/2026-11-19-release-0_26_0.md @@ -0,0 +1,90 @@ +--- +layout: post +title: "Kroxylicious release 0.26.0" +date: 2026-11-19 12:00:00 +0100 +author: "Keith Wall" +author_url: "https://github.com/k-wall" +# noinspection YAMLSchemaValidation +categories: blog kroxylicious-proxy releases +tags: [ "releases", "kroxylicious-proxy" ] +--- + +Kroxylicious 0.26.0 has hatched🐊! + +0.26.0 brings automatic downstream TLS certificate rotation, configurable post-quantum key exchange for both downstream and upstream TLS connections, client address visibility for filters, per-gateway PROXY protocol configuration, and container images for two new architectures. It also picks up a critical OpenJDK security fix. Take a look at [all the changes](https://github.com/kroxylicious/kroxylicious/blob/v0.26.0/CHANGELOG.md). + +--- + +### Security: Critical OpenJDK Fix (RHSA-2026:100567) + +Kroxylicious's container images build `java-21-openjdk-headless` from the UBI9 package repositories, so the 0.26.0 images incorporate Red Hat's [RHSA-2026:100567](https://access.redhat.com/errata/RHSA-2026:100567), published the day before this release. That advisory is rated **Critical** and fixes nine CVEs in OpenJDK 21, including CVE-2026-114938, a remote code execution vulnerability via memory corruption on x86-64 systems with AVX-512 VBMI. + +If you run the official Kroxylicious container images, upgrading to 0.26.0 picks up the fix. If you build your own images or run the proxy outside of our containers, make sure your JDK is patched independently. + +--- + +### Automatic Downstream TLS Certificate Rotation + +A long-standing request ([#104](https://github.com/kroxylicious/kroxylicious/issues/104)) is finally delivered: virtual cluster gateways now detect when their downstream TLS certificate or key material changes on disk and reload it automatically, with no proxy restart and no dropped connections. This is particularly useful alongside cert-manager or other automated certificate issuance pipelines. + +One known limitation: if the certificate files reach the container via a bind mount from a virtual machine host, a host-side change might not raise a filesystem notification inside the VM. Making the change from inside the container, or restarting the proxy, works around this. + +### Post-Quantum Key Exchange (PQC) + +Following [Design Proposal 144](https://github.com/kroxylicious/design/blob/main/proposals/144-pqc-support.md), both downstream (client-facing) and upstream (cluster-facing) TLS gain new configuration to control post-quantum key exchange algorithms. Gateways and clusters can set a `namedGroups` attribute with `allowed` and `denied` lists — `allowed` also sets key exchange preference order — so you can opt in to PQC algorithms, or lock a connection down to only accept them. This isn't enabled automatically; it's an opt-in configuration you apply where you need it. Support for the PQC algorithms themselves comes from the JDK and varies by provider and version prior to Java 27. + +### Client Address Visible to Filters + +Implementing [Proposal 139](https://github.com/kroxylicious/design/blob/main/proposals/139-expose-client-address-to-filters.md), `FilterContext` now exposes `clientAddress()`, `peerAddress()`, and `clientProxyProtocolContext()` to filters, so filter authors can make decisions based on where a connection actually originated — including through a PROXY protocol-aware load balancer. The `ProtocolLogger` filter has also been updated to include both addresses in its output. + +This is source-incompatible for anyone implementing `FilterContext` directly (e.g. a hand-rolled test double); filters that only consume a `FilterContext` are unaffected. + +### Per-Gateway PROXY Protocol Configuration + +**Breaking change:** PROXY protocol configuration has moved from the top-level proxy configuration to each `virtualClusters[].gateways[]` entry ([#5118](https://github.com/kroxylicious/kroxylicious/issues/5118), [#5263](https://github.com/kroxylicious/kroxylicious/pull/5263)). The `allowed` (auto-detect) mode has been removed, and `disabled` has been renamed `forbidden`, which is now the default. Move your `proxyProtocol` block inside each gateway that needs it, and rename `disabled` to `forbidden`. + +### New Container Architectures + +Proxy, operator, and admission webhook container images are now also published for `linux/ppc64le` and `linux/s390x` ([#4969](https://github.com/kroxylicious/kroxylicious/issues/4969)), in addition to the existing architectures. The proxy uses the NIO transport on these platforms. + +--- + +### Other Changes to Note + +- Maven 3.9.2+ is now required to build the project. +- A `matching /…/` regular expression literal in ACL rules files now keeps a backslash before any character other than `/` or `\` as part of the pattern, matching standard regex escaping rather than silently dropping it. +- Operator metrics have been migrated to the Java Operator SDK's `MicrometerMetricsV2` names and labels; dashboards and alerts using the previous `operator_sdk_` metrics will need updating. + +See the [CHANGELOG](https://github.com/kroxylicious/kroxylicious/blob/v0.26.0/CHANGELOG.md#0260) for the complete list of changes, deprecations, and removals. + +### Community Contributions + +This release included commits from: + +- [Abdullah](https://github.com/AzazelSensei) +- [Adam Pilkington](https://github.com/MarkNSweep) +- [Aditya Thakur](https://github.com/AdityaThakur1998) +- [Carles Arnal](https://github.com/carlesarnal) +- [Divyansh Kumar](https://github.com/Divyanshkumar62) +- [Francisco Vila](https://github.com/franvila) +- [henryZrncik](https://github.com/henryZrncik) +- [Julien Da Cunha](https://github.com/juliendcna) +- Keith Wall +- [Matheus André](https://github.com/matheusandre1) +- [Naitik Singh](https://github.com/ig-suyas) +- [OuO](https://github.com/mapan1984) +- Robert Young +- Sam Barker +- Tom Bentley +- [Uday Vishnu Patil](https://github.com/coder6955) +- [2748109647](https://github.com/2748109647) + +Thank you all, your hard work is massively appreciated! + +### Artefacts + +Download binary distributions and container images from the [download](https://kroxylicious.io/download/0.26.0/) page. + +### Feedback + +Drop by and say hello on [Slack](https://kroxylicious.slack.com), [GitHub](https://github.com/kroxylicious/kroxylicious/issues), or [bsky](https://bsky.app/profile/kroxylicious.io). You can also join us in person at a [community call]({% link join-us/community-call/index.md %}). From 65715db4c16894b4df8e1ebd531d9c685b1aca58 Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Thu, 19 Nov 2026 15:48:28 +0000 Subject: [PATCH 2/6] docs: clarify OpenJDK RPM is installed, not built Assisted-by: Claude Sonnet 5 Signed-off-by: Keith Wall --- _posts/2026-11-19-release-0_26_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2026-11-19-release-0_26_0.md b/_posts/2026-11-19-release-0_26_0.md index 5191a2f1..588fafa4 100644 --- a/_posts/2026-11-19-release-0_26_0.md +++ b/_posts/2026-11-19-release-0_26_0.md @@ -17,7 +17,7 @@ Kroxylicious 0.26.0 has hatched🐊! ### Security: Critical OpenJDK Fix (RHSA-2026:100567) -Kroxylicious's container images build `java-21-openjdk-headless` from the UBI9 package repositories, so the 0.26.0 images incorporate Red Hat's [RHSA-2026:100567](https://access.redhat.com/errata/RHSA-2026:100567), published the day before this release. That advisory is rated **Critical** and fixes nine CVEs in OpenJDK 21, including CVE-2026-114938, a remote code execution vulnerability via memory corruption on x86-64 systems with AVX-512 VBMI. +Kroxylicious's container images install `java-21-openjdk-headless` from the UBI9 package repositories, so the 0.26.0 images incorporate Red Hat's [RHSA-2026:100567](https://access.redhat.com/errata/RHSA-2026:100567), published the day before this release. That advisory is rated **Critical** and fixes nine CVEs in OpenJDK 21, including CVE-2026-114938, a remote code execution vulnerability via memory corruption on x86-64 systems with AVX-512 VBMI. If you run the official Kroxylicious container images, upgrading to 0.26.0 picks up the fix. If you build your own images or run the proxy outside of our containers, make sure your JDK is patched independently. From ee5fe9f8703ef697b3a852f2e67943a7b1323ded Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Thu, 19 Nov 2026 15:55:57 +0000 Subject: [PATCH 3/6] docs: give prominence to two ACL authorizer CVEs Add a dedicated Security Advisories section covering CVE-2026-118952 (GHSA-qvv3-6w3q-hgqc) and CVE-2026-128424 (GHSA-x5xx-3j9w-x63g), placed ahead of the feature highlights, and drop the now-redundant mention of the regex-escape fix further down the post. Assisted-by: Claude Sonnet 5 Signed-off-by: Keith Wall --- _posts/2026-11-19-release-0_26_0.md | 35 ++++++++++++++++++++++++++--- 1 file changed, 32 insertions(+), 3 deletions(-) diff --git a/_posts/2026-11-19-release-0_26_0.md b/_posts/2026-11-19-release-0_26_0.md index 588fafa4..9757c1fa 100644 --- a/_posts/2026-11-19-release-0_26_0.md +++ b/_posts/2026-11-19-release-0_26_0.md @@ -11,11 +11,41 @@ tags: [ "releases", "kroxylicious-proxy" ] Kroxylicious 0.26.0 has hatched🐊! -0.26.0 brings automatic downstream TLS certificate rotation, configurable post-quantum key exchange for both downstream and upstream TLS connections, client address visibility for filters, per-gateway PROXY protocol configuration, and container images for two new architectures. It also picks up a critical OpenJDK security fix. Take a look at [all the changes](https://github.com/kroxylicious/kroxylicious/blob/v0.26.0/CHANGELOG.md). +0.26.0 brings automatic downstream TLS certificate rotation, configurable post-quantum key exchange for both downstream and upstream TLS connections, client address visibility for filters, per-gateway PROXY protocol configuration, and container images for two new architectures. It also fixes two high-severity vulnerabilities in the ACL authorizer and picks up a critical OpenJDK security fix. Take a look at [all the changes](https://github.com/kroxylicious/kroxylicious/blob/v0.26.0/CHANGELOG.md). --- -### Security: Critical OpenJDK Fix (RHSA-2026:100567) +### Security Advisories + +#### CVE-2026-118952: Principal Type Confusion and Incomplete Prefix Matching in the ACL Authorizer + +**Affected:** Kroxylicious 0.18.0 through 0.25.1 when using the `kroxylicious-authorizer-acl` plugin with `like` (prefix) rules. + +**Not affected:** If you do not use the ACL authorizer, or you only use exact-match rules, you are not affected. + +**Description:** `AclAuthorizer`'s `TypeNameMap` used a single `TreeMap.floorEntry` lookup to resolve prefix rules. This had two consequences: a prefix rule written for one principal type (e.g. `Role`) could match a principal of a different type with the same name prefix, and when multiple prefixes overlapped, only the longest was ever checked, so a shorter, more restrictive rule could be silently skipped. Either way, authorization decisions could be more permissive than intended. + +**Fix:** Prefix lookups are now resolved with exact-match checks across all applicable prefixes, keyed by principal/resource type, so every matching rule is evaluated and type confusion can't occur. + +**Advisory:** [GHSA-qvv3-6w3q-hgqc](https://github.com/kroxylicious/kroxylicious/security/advisories/GHSA-qvv3-6w3q-hgqc) + +#### CVE-2026-128424: Overly Permissive Regex Unescaping in the ACL Authorizer + +**Affected:** Kroxylicious 0.18.0 through 0.25.1 when using the `kroxylicious-authorizer-acl` plugin with `matching /…/` regex rules containing backslash escapes. + +**Not affected:** If you do not use the ACL authorizer, or your `matching` rules contain no backslash escapes, you are not affected. + +**Description:** The code that unquotes `matching /…/` literals stripped the backslash from every `\X` escape sequence, not just `\/` and `\\`. This turned intentionally-literal regex metacharacters such as `\.`, `\d`, `\w`, `\s`, and `\b` into their broader regex meaning — for example, a rule meant to match only the literal topic `orders.v1` was silently enforced as a pattern where `.` matched any character — so rules could grant access more broadly than the operator intended, with no indication anything was wrong. + +**Fix:** Unescaping is now restricted to the two sequences that should be literal, `\/` and `\\`; every other backslash escape passes through unchanged to the regex engine. + +**Advisory:** [GHSA-x5xx-3j9w-x63g](https://github.com/kroxylicious/kroxylicious/security/advisories/GHSA-x5xx-3j9w-x63g) + +If you run the ACL authorizer with `like` or `matching` rules, upgrade to 0.26.0 and review your rules files for any that may have been relying on the old, overly-permissive behaviour. + +--- + +### Container Image: Critical OpenJDK Fix (RHSA-2026:100567) Kroxylicious's container images install `java-21-openjdk-headless` from the UBI9 package repositories, so the 0.26.0 images incorporate Red Hat's [RHSA-2026:100567](https://access.redhat.com/errata/RHSA-2026:100567), published the day before this release. That advisory is rated **Critical** and fixes nine CVEs in OpenJDK 21, including CVE-2026-114938, a remote code execution vulnerability via memory corruption on x86-64 systems with AVX-512 VBMI. @@ -52,7 +82,6 @@ Proxy, operator, and admission webhook container images are now also published f ### Other Changes to Note - Maven 3.9.2+ is now required to build the project. -- A `matching /…/` regular expression literal in ACL rules files now keeps a backslash before any character other than `/` or `\` as part of the pattern, matching standard regex escaping rather than silently dropping it. - Operator metrics have been migrated to the Java Operator SDK's `MicrometerMetricsV2` names and labels; dashboards and alerts using the previous `operator_sdk_` metrics will need updating. See the [CHANGELOG](https://github.com/kroxylicious/kroxylicious/blob/v0.26.0/CHANGELOG.md#0260) for the complete list of changes, deprecations, and removals. From 9dde0f4466045ed9068a81e0e02a11f5068d2a5a Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Thu, 19 Nov 2026 15:56:46 +0000 Subject: [PATCH 4/6] docs: lead with the OpenJDK fix Assisted-by: Claude Sonnet 5 Signed-off-by: Keith Wall --- _posts/2026-11-19-release-0_26_0.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/_posts/2026-11-19-release-0_26_0.md b/_posts/2026-11-19-release-0_26_0.md index 9757c1fa..4dabe85b 100644 --- a/_posts/2026-11-19-release-0_26_0.md +++ b/_posts/2026-11-19-release-0_26_0.md @@ -11,7 +11,15 @@ tags: [ "releases", "kroxylicious-proxy" ] Kroxylicious 0.26.0 has hatched🐊! -0.26.0 brings automatic downstream TLS certificate rotation, configurable post-quantum key exchange for both downstream and upstream TLS connections, client address visibility for filters, per-gateway PROXY protocol configuration, and container images for two new architectures. It also fixes two high-severity vulnerabilities in the ACL authorizer and picks up a critical OpenJDK security fix. Take a look at [all the changes](https://github.com/kroxylicious/kroxylicious/blob/v0.26.0/CHANGELOG.md). +0.26.0 picks up a critical OpenJDK security fix and resolves two high-severity vulnerabilities in the ACL authorizer. It also brings automatic downstream TLS certificate rotation, configurable post-quantum key exchange for both downstream and upstream TLS connections, client address visibility for filters, per-gateway PROXY protocol configuration, and container images for two new architectures. Take a look at [all the changes](https://github.com/kroxylicious/kroxylicious/blob/v0.26.0/CHANGELOG.md). + +--- + +### Container Image: Critical OpenJDK Fix (RHSA-2026:100567) + +Kroxylicious's container images install `java-21-openjdk-headless` from the UBI9 package repositories, so the 0.26.0 images incorporate Red Hat's [RHSA-2026:100567](https://access.redhat.com/errata/RHSA-2026:100567), published the day before this release. That advisory is rated **Critical** and fixes nine CVEs in OpenJDK 21, including CVE-2026-114938, a remote code execution vulnerability via memory corruption on x86-64 systems with AVX-512 VBMI. + +If you run the official Kroxylicious container images, upgrading to 0.26.0 picks up the fix. If you build your own images or run the proxy outside of our containers, make sure your JDK is patched independently. --- @@ -45,14 +53,6 @@ If you run the ACL authorizer with `like` or `matching` rules, upgrade to 0.26.0 --- -### Container Image: Critical OpenJDK Fix (RHSA-2026:100567) - -Kroxylicious's container images install `java-21-openjdk-headless` from the UBI9 package repositories, so the 0.26.0 images incorporate Red Hat's [RHSA-2026:100567](https://access.redhat.com/errata/RHSA-2026:100567), published the day before this release. That advisory is rated **Critical** and fixes nine CVEs in OpenJDK 21, including CVE-2026-114938, a remote code execution vulnerability via memory corruption on x86-64 systems with AVX-512 VBMI. - -If you run the official Kroxylicious container images, upgrading to 0.26.0 picks up the fix. If you build your own images or run the proxy outside of our containers, make sure your JDK is patched independently. - ---- - ### Automatic Downstream TLS Certificate Rotation A long-standing request ([#104](https://github.com/kroxylicious/kroxylicious/issues/104)) is finally delivered: virtual cluster gateways now detect when their downstream TLS certificate or key material changes on disk and reload it automatically, with no proxy restart and no dropped connections. This is particularly useful alongside cert-manager or other automated certificate issuance pipelines. From 0b716efc328f6f0bb8c4eb40fbf3ebece12e2c1e Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Thu, 19 Nov 2026 15:57:47 +0000 Subject: [PATCH 5/6] docs: focus CVE-2026-118952 description on user impact Drop the TypeNameMap/TreeMap.floorEntry implementation detail in favour of describing how the bug affects authorization outcomes. Assisted-by: Claude Sonnet 5 Signed-off-by: Keith Wall --- _posts/2026-11-19-release-0_26_0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2026-11-19-release-0_26_0.md b/_posts/2026-11-19-release-0_26_0.md index 4dabe85b..3e6309d8 100644 --- a/_posts/2026-11-19-release-0_26_0.md +++ b/_posts/2026-11-19-release-0_26_0.md @@ -31,9 +31,9 @@ If you run the official Kroxylicious container images, upgrading to 0.26.0 picks **Not affected:** If you do not use the ACL authorizer, or you only use exact-match rules, you are not affected. -**Description:** `AclAuthorizer`'s `TypeNameMap` used a single `TreeMap.floorEntry` lookup to resolve prefix rules. This had two consequences: a prefix rule written for one principal type (e.g. `Role`) could match a principal of a different type with the same name prefix, and when multiple prefixes overlapped, only the longest was ever checked, so a shorter, more restrictive rule could be silently skipped. Either way, authorization decisions could be more permissive than intended. +**Description:** A `like` (prefix) rule written for one principal type (e.g. `Role`) could incorrectly match a principal of a different type that happens to share the same name prefix, and when rules had overlapping prefixes, a shorter, more restrictive rule could be silently skipped in favour of a longer one. In both cases, access could be granted that the rules file did not intend — with no indication that anything was wrong. -**Fix:** Prefix lookups are now resolved with exact-match checks across all applicable prefixes, keyed by principal/resource type, so every matching rule is evaluated and type confusion can't occur. +**Fix:** Prefix matching now checks principal/resource type correctly and evaluates every applicable prefix, not just one, so rules are enforced as written. **Advisory:** [GHSA-qvv3-6w3q-hgqc](https://github.com/kroxylicious/kroxylicious/security/advisories/GHSA-qvv3-6w3q-hgqc) From b6e43f476e25b408cf369e5a8a14188b7f470f19 Mon Sep 17 00:00:00 2001 From: Keith Wall Date: Thu, 19 Nov 2026 18:41:41 +0000 Subject: [PATCH 6/6] tweaks Signed-off-by: Keith Wall --- _posts/2026-11-19-release-0_26_0.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/_posts/2026-11-19-release-0_26_0.md b/_posts/2026-11-19-release-0_26_0.md index 3e6309d8..d978fd9b 100644 --- a/_posts/2026-11-19-release-0_26_0.md +++ b/_posts/2026-11-19-release-0_26_0.md @@ -57,8 +57,6 @@ If you run the ACL authorizer with `like` or `matching` rules, upgrade to 0.26.0 A long-standing request ([#104](https://github.com/kroxylicious/kroxylicious/issues/104)) is finally delivered: virtual cluster gateways now detect when their downstream TLS certificate or key material changes on disk and reload it automatically, with no proxy restart and no dropped connections. This is particularly useful alongside cert-manager or other automated certificate issuance pipelines. -One known limitation: if the certificate files reach the container via a bind mount from a virtual machine host, a host-side change might not raise a filesystem notification inside the VM. Making the change from inside the container, or restarting the proxy, works around this. - ### Post-Quantum Key Exchange (PQC) Following [Design Proposal 144](https://github.com/kroxylicious/design/blob/main/proposals/144-pqc-support.md), both downstream (client-facing) and upstream (cluster-facing) TLS gain new configuration to control post-quantum key exchange algorithms. Gateways and clusters can set a `namedGroups` attribute with `allowed` and `denied` lists — `allowed` also sets key exchange preference order — so you can opt in to PQC algorithms, or lock a connection down to only accept them. This isn't enabled automatically; it's an opt-in configuration you apply where you need it. Support for the PQC algorithms themselves comes from the JDK and varies by provider and version prior to Java 27. @@ -67,8 +65,6 @@ Following [Design Proposal 144](https://github.com/kroxylicious/design/blob/main Implementing [Proposal 139](https://github.com/kroxylicious/design/blob/main/proposals/139-expose-client-address-to-filters.md), `FilterContext` now exposes `clientAddress()`, `peerAddress()`, and `clientProxyProtocolContext()` to filters, so filter authors can make decisions based on where a connection actually originated — including through a PROXY protocol-aware load balancer. The `ProtocolLogger` filter has also been updated to include both addresses in its output. -This is source-incompatible for anyone implementing `FilterContext` directly (e.g. a hand-rolled test double); filters that only consume a `FilterContext` are unaffected. - ### Per-Gateway PROXY Protocol Configuration **Breaking change:** PROXY protocol configuration has moved from the top-level proxy configuration to each `virtualClusters[].gateways[]` entry ([#5118](https://github.com/kroxylicious/kroxylicious/issues/5118), [#5263](https://github.com/kroxylicious/kroxylicious/pull/5263)). The `allowed` (auto-detect) mode has been removed, and `disabled` has been renamed `forbidden`, which is now the default. Move your `proxyProtocol` block inside each gateway that needs it, and rename `disabled` to `forbidden`. @@ -98,13 +94,13 @@ This release included commits from: - [Francisco Vila](https://github.com/franvila) - [henryZrncik](https://github.com/henryZrncik) - [Julien Da Cunha](https://github.com/juliendcna) -- Keith Wall +- [Keith Wall](https://github.com/k-wall) - [Matheus André](https://github.com/matheusandre1) - [Naitik Singh](https://github.com/ig-suyas) - [OuO](https://github.com/mapan1984) -- Robert Young -- Sam Barker -- Tom Bentley +- [Robert Young](https://github.com/robobario) +- [Sam Barker](https://github.com/SamBarker) +- [Tom Bentley](https://github.com/tombentley) - [Uday Vishnu Patil](https://github.com/coder6955) - [2748109647](https://github.com/2748109647)