critical

CVE

CVE-2026-121952, CVE-2026-121953, CVE-2026-121392, CVE-2026-121964, CVE-2026-121958, CVE-2026-121951, CVE-2026-121955, CVE-2026-121956, CVE-2026-121957, CVE-2026-121960, CVE-2026-121961, CVE-2026-121963, CVE-2026-121386, CVE-2026-121398, CVE-2026-121409, CVE-2026-100252, CVE-2026-100300, CVE-2026-115448, CVE-2026-100235, CVE-2026-100302, CVE-2026-119084, CVE-2026-121621, CVE-2026-68524, CVE-2026-73577, CVE-2026-73578, CVE-2026-83542

CWE

CWE-787, CWE-416, CWE-295, CWE-285, CWE-674, CWE-470, CWE-78

Affected Surface

  • FreeRDP (`freerdp`, `libfreerdp`, `freerdp-proxy`, `libwinpr`) versions `< 3.32.2` (14 CVEs including `CVE-2026-121952`, `CVE-2026-121953`, `CVE-2026-121392`, `CVE-2026-121964`, and `CVE-2026-121958`)
  • Apache ZooKeeper (`org.apache.zookeeper:zookeeper`) `3.9.0` through `3.9.6` and `3.8.0` through `3.8.7` (fixed in `3.9.7` and `3.8.8`)
  • Maven `com.amazon.redshift:redshift-jdbc42` `< 2.3.0` (`CVE-2026-119084` / `GHSA-qrph-v96m-w2mv`, CVSS 9.2 Critical) and Go `github.com/argoproj-labs/argocd-image-updater` (`CVE-2026-121621`, CVSS 8.8 High)
  • Apache OFBiz deployments `< 24.09.08` (`CVE-2026-68524`, `CVE-2026-73577`, `CVE-2026-73578`, `CVE-2026-83542`, and 17 companion CVEs)

TL;DR

On 3 and 4 November 2026, security advisories across FreeRDP, Apache ZooKeeper, Amazon Redshift JDBC Driver, Argo CD Image Updater, and Apache OFBiz disclosed critical remote code execution, memory corruption, and authentication-bypass vulnerabilities:

  1. FreeRDP 3.32.2 (14 CVEs led by CVE-2026-121952, CVE-2026-121953, and CVE-2026-121392, up to CVSS 9.3 Critical): FreeRDP 3.32.2 fixes 14 client, server, and proxy vulnerabilities. Three are rated Critical: CVE-2026-121952 (GHSA-xc85-4mqc-xgcx, CVSS 9.3) is a heap out-of-bounds write and heap-memory leak in freerdp-proxy when a connecting client sends a Confirm Active PDU with numCellCaches < 5; CVE-2026-121953 (GHSA-6wqx-rv3q-vcxp, CVSS 9.3) is a client use-after-free in the rdpgfx dynamic virtual channel triggered when a server opens a second channel under the same DVC name with a new ChannelId and closes one; and CVE-2026-121392 (GHSA-jq25-3374-4262, CVSS 9.1) fixes an incomplete patch from 3.29.0 (GHSA-43hh-p3vw-hfx3) that left Common Name fallback and IP-literal DNS-SAN matching unpatched in tls_verify_certificate(). Eleven High-severity CVEs also fix an RD Gateway RPC client heap overflow (CVE-2026-121964), an RDPGFX 16-bit surface-key truncation heap OOB write (CVE-2026-121958), and multiple UAF/double-free bugs.
  2. Apache ZooKeeper 3.9.7 and 3.8.8 (CVE-2026-100252 CVSS 8.6, CVE-2026-100300 CVSS 8.7, CVE-2026-115448 CVSS 8.7, CVE-2026-100235, CVE-2026-100302): In CVE-2026-100252, ZooKeeper’s SASL callback handler accepted any client-supplied authorization ID (authzid) before attempting zookeeper.security.auth_to_local principal canonicalization; if no rule matched (such as a principal from a cross-realm Kerberos trust), canonicalization logged an error and kept the client’s requested authzid, allowing the client to impersonate zookeeper.superUser. Worse, CVE-2026-100300 and CVE-2026-115448 allow unauthenticated clients on default deployments to permanently brick the ensemble’s on-disk data directory by writing malformed quota nodes under /zookeeper/quota or creating deeply nested znode chains that overflow the JVM stack during startup snapshot serialization.
  3. Amazon Redshift JDBC Driver 2.3.0 (CVE-2026-119084, CVSS 9.2 Critical), Argo CD Image Updater (CVE-2026-121621, CVSS 8.8 High), and Apache OFBiz 24.09.08 (CVE-2026-68524, CVE-2026-73578, CVE-2026-83542): Redshift JDBC Driver < 2.3.0 performed unsafe reflection on connection URL parameters and AWS credentials profiles (and defaulted sslmode to verify-ca instead of verify-full); Argo CD Image Updater interpolated SSH Git repository proxy URLs unsanitized into shell-interpreted GIT_SSH_COMMAND strings; and Apache OFBiz < 24.09.08 patched 21 CVEs including three unauthenticated pre-auth RCE paths via screen-definition loading (CVE-2026-68524), saved-view authorization bypass (CVE-2026-73578), and login-page widget injection (CVE-2026-83542).

What to do now: Upgrade FreeRDP to >= 3.32.2, Apache ZooKeeper to 3.9.7 or 3.8.8 (and remove default OPEN_ACL_UNSAFE root/quota permissions), com.amazon.redshift:redshift-jdbc42 to >= 2.3.0, Argo CD Image Updater to a build containing PR #1905, and Apache OFBiz to >= 24.09.08.

Affected packages and projects

EcosystemPackage / ProjectCVE / AdvisorySeverityAffected versionsFixed versionVulnerable component
C / LinuxFreeRDP (libfreerdp, freerdp-proxy, libwinpr)CVE-2026-121952, CVE-2026-121953, CVE-2026-121392, CVE-2026-121964, CVE-2026-121958, and 9 companion CVEsCritical (9.3 / 9.1) & High (8.2..8.7)< 3.32.23.32.2capabilities.c, drdynvc_main.c, tls.c, rpc_client.c, rdpgfx_main.c, HashTable.c
Maven / Javaorg.apache.zookeeper:zookeeperCVE-2026-100252, CVE-2026-100300, CVE-2026-115448, CVE-2026-100235, CVE-2026-100302High (8.7 / 8.6 / 7.1) & Medium (6.0)3.9.0..3.9.6, 3.8.0..3.8.73.9.7, 3.8.8Client-port SASL callback handler, /zookeeper/quota parser, snapshot recursion, setACL, and multiRead
Maven / Javacom.amazon.redshift:redshift-jdbc42CVE-2026-119084 (GHSA-qrph-v96m-w2mv, AWS-2026-168)Critical (9.2)< 2.3.02.3.0Unsafe class loading in JDBC URL connection parameters and AWS credentials profiles
Go / Containersgithub.com/argoproj-labs/argocd-image-updaterCVE-2026-121621High (8.8)Prior to PR #1905Patched in PR #1905Unsanitized SSH repository proxy URL interpolated into GIT_SSH_COMMAND in ext/git/creds.go
Java / ERPApache OFBizCVE-2026-68524, CVE-2026-73577, CVE-2026-73578, CVE-2026-83542, and 17 companion CVEsCritical / High< 24.09.0824.09.08Screen-definition loading, path-suffix and saved-view auth checks, FreeMarker renderLink, and Groovy sandbox

Technical analysis

1. FreeRDP 3.32.2: Proxy heap OOB write (CVE-2026-121952), rdpgfx UAF (CVE-2026-121953), RD Gateway overflow (CVE-2026-121964), and 16-bit surface key truncation (CVE-2026-121958)

Four of the 14 FreeRDP 3.32.2 advisories expose distinct memory-corruption bugs across client and proxy deployments:

  • Proxy BitmapCacheV2CellInfo out-of-bounds write (CVE-2026-121952 / GHSA-xc85-4mqc-xgcx, CVSS 9.3): In libfreerdp/core/capabilities.c, rdp_read_bitmap_cache_v2_capability_set() checked only the upper bound if (numCellCaches > 5) return FALSE;. When a client connecting to freerdp-proxy sent a Confirm Active PDU with numCellCaches between 0 and 4, the proxy resized BitmapCacheV2CellInfo to that smaller count, but when the proxy subsequently built its own Confirm Active PDU for the backend server, it indexed BitmapCacheV2CellInfo[0..4] unconditionally, writing 4 bytes past the heap buffer and serializing adjacent heap memory to the backend.
  • Client rdpgfx dynamic virtual channel UAF (CVE-2026-121953 / GHSA-6wqx-rv3q-vcxp, CVSS 9.3): In channels/drdynvc/client/drdynvc_main.c, dvcman_create_channel() verified that the server’s ChannelId was unused, but did not check whether another active channel already used the same ChannelName. Because generic_on_new_channel_connection() (channels/client/generic_dynvc.c:56-57) stored only a single channel_callback pointer per listener, a malicious RDP server could open a second "Microsoft::Windows::RDS::Graphics" channel under a new ChannelId (overwriting the callback slot), close it (freeing the callback without clearing the pointer), and send data on the still-open first channel to dereference freed heap memory.
  • RD Gateway rpc_client_recv_fragment heap overflow (CVE-2026-121964 / GHSA-q82v-5wjg-6h57, CVSS 8.7): In libfreerdp/core/gateway/rpc_client.c (lines 520-550), the BIND_ACK and ALTER_CONTEXT_RESP branch called Stream_EnsureCapacity(pdu->s, len) before Stream_Write(pdu->s, Stream_Buffer(fragment), len). Because Stream_EnsureCapacity checks total buffer capacity rather than remaining capacity from the current stream offset (Stream_EnsureRemainingCapacity), sending a BIND_ACK after pdu->s had already advanced allowed a single fragment to overrun the 4096-byte heap buffer by ~3904 bytes.
  • RDPGFX surface hash-key 16-bit truncation (CVE-2026-121958 / GHSA-m59q-wm7v-mp57, CVSS 8.7): rdpgfx_main.c stores surfaces in a WinPR hash table under key = (void*)(uintptr_t)(surfaceId + 1). When surfaceId == 0xFFFF, key is 0x10000. However, the per-surface delete callback cast the key back as const UINT16 id = (UINT16)(uintptr_t)key; if (id < 1) return FALSE;, truncating 0x10000 to 0 so the entry failed deletion while HashTable_GetKeys() (winpr/libwinpr/utils/collections/HashTable.c:555-611) allocated calloc(numOfElements, ...) and wrote pKeys[iKey++] past the end of the array.

2. Apache ZooKeeper 3.9.7 and 3.8.8: SASL authzid superuser escalation (CVE-2026-100252) and persistent ensemble bricking (CVE-2026-100300, CVE-2026-115448)

  • SASL authzid bypass (CVE-2026-100252, CVSS 8.6): When SASL authentication is enabled on ZooKeeper’s client port, the server’s SASL callback handler accepted any authorization identity (authzid) requested by the client without comparing it to the authenticated principal (authn), relying on a subsequent step to overwrite the session identity with the canonicalized zookeeper.security.auth_to_local principal. When no auth_to_local rule matched the authenticated principal (for example, a Kerberos principal from a cross-realm trusted KDC), canonicalization threw an exception that the server merely logged, leaving the unverified client-supplied authzid active for all sasl: ACL checks, including zookeeper.superUser.
  • Unauthenticated persistent DoS (CVE-2026-100300 and CVE-2026-115448, CVSS 8.7): On default ZooKeeper deployments where / and /zookeeper/quota carry OPEN_ACL_UNSAFE, any client can write malformed quota data under /zookeeper/quota (CVE-2026-100300, crashing the critical transaction-apply thread) or create a chain of deeply nested znodes within jute.maxbuffer (CVE-2026-115448 / ZOOKEEPER-5097, overflowing the JVM stack during recursive snapshot serialization). Because ZooKeeper replays its transaction log and takes a snapshot on startup, both attacks leave the on-disk data directory permanently unbootable across the leader and all followers.

3. Argo CD Image Updater GIT_SSH_COMMAND injection (CVE-2026-121621), Amazon Redshift JDBC 2.3.0 (CVE-2026-119084), and Apache OFBiz 24.09.08

In argoproj-labs/argocd-image-updater (PR #1905), ext/git/creds.go previously passed the proxy URL configured for an SSH Git repository directly into GIT_SSH_COMMAND (which git executes through /bin/sh -c). An authenticated user able to configure an SSH repository proxy URL could inject shell metacharacters to execute arbitrary commands and dump Kubernetes secrets inside the Image Updater pod. PR #1905 validates proxy schemes (socks5, socks5h for SSH; http, https, socks5, socks5h for HTTPS) and enforces a strict hostname regular expression:

// ext/git/creds.go (argoproj-labs/argocd-image-updater PR #1905)
var validProxyHostRegexp = regexp.MustCompile(`^[a-zA-Z0-9.\-]+$`)

func validateProxyURL(rawURL string) error {
	return validateProxyURLWithSchemes(rawURL, "socks5", "socks5h")
}

func ValidateHTTPProxyURL(rawURL string) error {
	return validateProxyURLWithSchemes(rawURL, "http", "https", "socks5", "socks5h")
}

In com.amazon.redshift:redshift-jdbc42 (CVE-2026-119084 / GHSA-qrph-v96m-w2mv, fixed in 2.3.0), connection parameter and AWS credentials profile handlers used unsafe reflection to instantiate classes from the application classpath when given attacker-influenced JDBC connection URLs or profile properties. Version 2.3.0 also switches RedshiftDataSource serialization from Java object serialization to primitive fields and changes the default sslmode from verify-ca to verify-full.

Detection and remediation

# 1. Check installed FreeRDP client/proxy versions on Linux workstations and jump hosts
xfreerdp --version 2>/dev/null || freerdp-proxy --version 2>/dev/null || true
dpkg -l '*freerdp*' 2>/dev/null || rpm -qa '*freerdp*' 2>/dev/null || true

# 2. Search Maven / Gradle files for vulnerable ZooKeeper (< 3.9.7 / < 3.8.8) and Redshift JDBC (< 2.3.0)
rg -n '(org\.apache\.zookeeper|redshift-jdbc42)' pom.xml build.gradle* **/pom.xml 2>/dev/null

# 3. Check Kubernetes clusters for argocd-image-updater images and Apache OFBiz versions
kubectl get pods -A -o jsonpath='{range .items[*]}{.metadata.namespace}{"/"}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}' 2>/dev/null | grep -i 'argocd-image-updater' || true
  1. Upgrade FreeRDP to >= 3.32.2: Prioritize jump hosts, VDI clients, and freerdp-proxy gateways exposed to untrusted RDP clients or servers.
  2. Upgrade Apache ZooKeeper to 3.9.7 or 3.8.8 and lock down ACLs: Restrict write access on / and /zookeeper/quota instead of leaving OPEN_ACL_UNSAFE enabled, and ensure zookeeper.security.auth_to_local explicitly maps or rejects all cross-realm principals.
  3. Upgrade Amazon Redshift JDBC Driver to >= 2.3.0, Argo CD Image Updater, and Apache OFBiz to >= 24.09.08: Reject untrusted JDBC connection URL properties (socketFactory, plugin class names, custom credential providers) in multi-tenant BI/data connectors, and upgrade Internet-facing Apache OFBiz servers to 24.09.08 immediately.

Timeline

  • 2026-10-12: AWS releases Amazon Redshift JDBC Driver 2.3.0 on Maven Central and GitHub.
  • 2026-11-03 (15:17 to 22:19 UTC): Apache announces ZooKeeper 3.9.7 and 3.8.8 on oss-security (2026/11/03/9 through 13); NVD and AWS publish CVE-2026-119084 (AWS-2026-168, GHSA-qrph-v96m-w2mv) for Redshift JDBC Driver and CVE-2026-121621 for Argo CD Image Updater.
  • 2026-11-04 (15:17 to 16:17 UTC): NVD publishes the 14 FreeRDP 3.32.2 CVEs (CVE-2026-121951 through CVE-2026-121964, CVE-2026-121386 through CVE-2026-121409), and Apache announces OFBiz 24.09.08 (oss-security 2026/11/04/9).

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References