Version 1.21.x#
Release notes for Nubus for Kubernetes 1.21.x:
Version 1.21.0 - 2026-07-20#
This is the thirty-second production release of Nubus for Kubernetes.
Upgrade path
For the upgrade to version 1.21.0, your deployment must run on version 1.20.x. For the general steps to upgrade an existing Nubus for Kubernetes deployment, see Upgrade in Univention Nubus for Kubernetes - Operation Manual [1].
Changes#
This section lists the changes in 1.21.0 grouped by component in Nubus for Kubernetes.
Keycloak service#
Fix a regression introduced in 1.19.1 where the Keycloak LDAP user federation bound the service account again for every operation instead of reusing the pooled connection. Under load, this flooded the LDAP server with
BINDrequests. The service account now binds once and reuses the connection.Fix sign-in failures with
HTTP 401in Portal and UMC after a username changes only in letter case, for example fromFOOtofoo. Keycloak kept serving the cacheduiduntil its imported user cache expired. The LDAP user federation no longer caches imported users and always reads theuidfrom the LDAP server so that a renamed user can sign in immediately. The upgrade immediately applies the setting.Upgrade Keycloak to version 26.7.0. This includes fixes for the following security findings:
These changes don’t require operator action.
Keycloak Extensions#
Align the securityContext.enabled setting of Keycloak Extensions
with the other Nubus for Kubernetes Helm Charts:
nubusKeycloakExtensions.handler.podSecurityContext.enablednubusKeycloakExtensions.proxy.podSecurityContext.enabled
The rendered template output now always omits the enabled key.
Setting the value to false deactivates the security context.
UDM HTTP REST API#
Improve probes for the UDM HTTP REST API.
The liveness and readiness probes now send HTTP requests to the service
through the probe script /usr/local/bin/univention-probe-udm.py
shipped in the container image.
The probes now behave as follows:
The readiness probe fails when the LDAP server is unreachable, so Kubernetes routes traffic away from pods that can’t serve requests.
The liveness probe only fails when the service doesn’t answer at all, so an LDAP outage doesn’t cause pod restarts.
UMC server#
Improve UMC server probes. Previously, the probes only checked whether the service port accepted TCP connections. The liveness and readiness probes of the UMC server container now verify that the service answers requests.
Replace the placeholder probes of the SSSD sidecar container, which unconditionally reported success. The liveness probe now queries the SSSD NSS responder without depending on the LDAP server, so a hung responder restarts the container while an LDAP outage doesn’t. The readiness probe verifies the whole lookup path from NSS through SSSD to the LDAP server.
The UMC gateway probes now verify that the web server answers requests.
Provisioning Service#
Fix an issue where the Provisioning Service could delay redelivery of an unacknowledged event by up to 30 seconds. If a consumer received an event but didn’t confirm it, for example because it restarted or was temporarily unavailable, the service redelivered the event only after a long, fixed wait. As a result, downstream services could receive directory updates with a noticeable delay. The service now redelivers such events within about one second, so consumers catch up quickly after a disruption.
Improve the durability of queued events. The message store flushes events to disk shortly after receiving them, which reduces the risk of losing events if a node or pod stops unexpectedly. This change slightly increases per-event latency. The flush interval is configurable through the Helm Chart value
nubusProvisioning.nats.config.jetstream.fileStore.sync_interval, which defaults to10ms.These changes also upgrade the embedded NATS message broker to version 2.14.3.
Portal#
Fix a data exposure on portals that require sign-in. The Portal rendered tiles to anonymous visitors and included them in the portal data before redirecting anonymous visitors to the sign-in page.
When a portal has the Users are required to login option enabled, the Portal now redirects anonymous visitors to the sign-in page before it renders or serves any categories, tiles, folders, or menu entries. Tiles without a group restriction appear for all users, so anonymous visitors could see them.
Guardian#
Nubus for Kubernetes removes the Guardian component
and its container images from the umbrella chart.
This removal prepares an upcoming change
and doesn’t alter the behavior of your deployment.
If you set any nubusGuardian.* values in your custom Helm Chart values,
you can remove them because they no longer have any effect.
Structured logging#
Despite prior announcements, Nubus for Kubernetes 1.21 doesn’t enable structured logging by default. Plain logging remains the default.
Nubus for Kubernetes 1.22 changes the default to structured logging.
To keep plain logging in your deployment,
Univention recommends setting all structured-logging configuration options to false.
Univention will mark plain logging as deprecated
and remove it in a future release.
For details,
see Logging
in Univention Nubus for Kubernetes - Operation Manual [1].
Included errata updates#
The errata updates contain fixes for the following CVEs:
- Authlib
CVE-2026-41425 (medium)
CVE-2026-41479 (medium)
CVE-2026-44681 (medium)
- Pillow
CVE-2024-28219 (medium)
- bind9-dnsutils
CVE-2026-3592 (medium)
CVE-2026-5950 (medium)
- bind9-host
CVE-2026-3592 (medium)
CVE-2026-5950 (medium)
- bind9-libs
CVE-2026-3592 (medium)
CVE-2026-5950 (medium)
- brace-expansion
CVE-2026-33750 (high)
CVE-2026-45149 (high)
- cryptography
CVE-2026-39892 (critical)
- dulwich
CVE-2026-47734 (medium)
- github.com/containerd/containerd/v2
CVE-2026-50195 (critical)
CVE-2026-53492 (critical)
CVE-2026-46680 (high)
CVE-2026-53488 (high)
CVE-2026-47262 (medium)
CVE-2026-53489 (medium)
- go.opentelemetry.io/otel
CVE-2026-29181 (high)
- go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp
CVE-2026-39882 (medium)
- golang.org/x/crypto
CVE-2026-39830 (critical)
CVE-2026-39831 (critical)
CVE-2026-39832 (critical)
CVE-2026-39833 (critical)
CVE-2026-39834 (critical)
CVE-2026-42508 (critical)
CVE-2026-46595 (critical)
CVE-2026-39829 (high)
CVE-2026-46597 (high)
CVE-2026-39827 (medium)
CVE-2026-39828 (medium)
CVE-2026-39835 (medium)
CVE-2026-46598 (medium)
- golang.org/x/net
CVE-2026-39821 (critical)
CVE-2026-33814 (high)
CVE-2026-25680 (medium)
CVE-2026-25681 (medium)
CVE-2026-27136 (medium)
CVE-2026-42502 (medium)
CVE-2026-42506 (medium)
CVE-2026-46600 (unknown)
- golang.org/x/sys
CVE-2026-39824 (low)
- golang.org/x/text
CVE-2026-56852 (unknown)
- keycloak-services
CVE-2026-9793 (high)
CVE-2026-9795 (high)
CVE-2026-9689 (medium)
CVE-2026-9798 (medium)
- libc-ares2
CVE-2026-33630 (unknown)
- libfreetype6
CVE-2026-50811 (medium)
- libglib2.0-0
CVE-2026-1484 (medium)
CVE-2026-1489 (medium)
CVE-2026-0988 (low)
CVE-2026-1485 (low)
- libgnutls30
CVE-2026-3832 (low)
- libgssapi-krb5-2
CVE-2026-40355 (high)
CVE-2026-40356 (high)
- libk5crypto3
CVE-2026-40355 (high)
CVE-2026-40356 (high)
- libkrb5-3
CVE-2026-40355 (high)
CVE-2026-40356 (high)
- libkrb5support0
CVE-2026-40355 (high)
CVE-2026-40356 (high)
- libopenjp2-7
CVE-2026-6192 (low)
- libpq5
CVE-2026-6472 (medium)
CVE-2026-6474 (medium)
CVE-2026-6478 (medium)
- libssh2-1
CVE-2026-58051 (medium)
- netty-codec-haproxy
CVE-2026-44893 (high)
CVE-2026-48059 (high)
- netty-codec-http
CVE-2026-50020 (medium)
- netty-codec-http2
CVE-2026-48043 (high)
CVE-2026-47244 (medium)
CVE-2026-50560 (medium)
- netty-handler
CVE-2026-44249 (high)
CVE-2026-45416 (high)
CVE-2026-50010 (high)
- netty-resolver-dns
CVE-2026-45674 (critical)
CVE-2026-47691 (critical)
CVE-2026-45673 (medium)
- netty-transport-native-epoll
CVE-2026-45536 (medium)
- nginx
CVE-2026-27784 (high)
CVE-2026-40701 (medium)
CVE-2026-42934 (medium)
CVE-2026-28753 (low)
- nginx-common
CVE-2026-27784 (high)
CVE-2026-40701 (medium)
CVE-2026-42934 (medium)
CVE-2026-28753 (low)
- oras.land/oras-go/v2
CVE-2026-50151 (high)
CVE-2026-50163 (high)
CVE-2026-50162 (medium)
CVE-2026-48978 (low)
- poetry
CVE-2026-41140 (high)
CVE-2026-34591 (medium)
- postcss
CVE-2026-41305 (medium)
- postgresql-client-15
CVE-2026-6472 (medium)
CVE-2026-6474 (medium)
CVE-2026-6478 (medium)
- pytest
CVE-2025-71176 (medium)
- python3-m2crypto
CVE-2009-0127 (medium)
- serialize-javascript
CVE-2026-34043 (high)
- stdlib
CVE-2026-32281 (high)
CVE-2026-32283 (high)
CVE-2026-33811 (high)
CVE-2026-33814 (high)
CVE-2026-39820 (high)
CVE-2026-39822 (high)
CVE-2026-39836 (high)
CVE-2026-42499 (high)
CVE-2026-42504 (high)
CVE-2025-61727 (medium)
CVE-2025-61728 (medium)
CVE-2025-61730 (medium)
CVE-2026-27142 (medium)
CVE-2026-27145 (medium)
CVE-2026-32282 (medium)
CVE-2026-32288 (medium)
CVE-2026-32289 (medium)
CVE-2026-39823 (medium)
CVE-2026-39825 (medium)
CVE-2026-39826 (medium)
CVE-2026-42505 (medium)
CVE-2026-42507 (medium)
CVE-2026-27139 (low)
- urllib3
CVE-2026-44432 (high)
- uuid
CVE-2026-41907 (high)