CODERED VTA

KubeVirt Update for openSUSE Leap 16 Fixes Eleven Go Library Security Flaws

High
Cabling behind data centre racks
Photo by D Coetzee on Flickr

openSUSE has published advisory openSUSE-SU-2026:22331-1, an update for the kubevirt1.8 stack on openSUSE Leap 16.0 that resolves eleven vulnerabilities and nine bug fixes. The advisory carries a vendor rating of important, and the highest-scoring issue, CVE-2026-84303, is rated 9.1 under both CVSS 3.1 and CVSS 4.0. All of the flaws sit in third-party Go libraries that KubeVirt links into its binaries rather than in KubeVirt's own virtualization logic: golang.org/x/crypto/ssh, golang.org/x/net/http2 and google.golang.org/grpc. Because those libraries are compiled into every component, the fix touches the whole package set, including virt-api, virt-controller, virt-handler, virt-launcher, virt-operator, virt-exportproxy, virt-exportserver, the synchronization controller and virtctl. Fixed packages are published at version 1.8.4-160000.3.1 for openSUSE Leap 16.0, built with Go 1.26 because the updated modules require it.

The advisory describes each defect at the library level. CVE-2026-56854, CVE-2026-56855 and CVE-2026-78662 cover an authentication bypass and deadlock conditions in the crypto/ssh library, with the bypass scored 8.1 and requiring only low privileges over the network. Four HTTP/2 issues affect the x/net stack: memory exhaustion driven by Trailer headers (CVE-2026-78659), a transport that accepts malformed framing-related headers (CVE-2026-78660), a double flow-control refund on server streams (CVE-2026-78663), and excessive CPU consumption triggered by repeated initial window changes (CVE-2026-78669). CVE-2026-97032 is a server crash caused by a race in the HPACK encoder. On the gRPC side, CVE-2026-84303 allows authorization policies enforced by the xDS RBAC HTTP filter to be bypassed using mixed-case or canonical-case header matches, CVE-2026-84304 permits heap memory exhaustion through fragmented HTTP/2 DATA frames, and CVE-2026-84445 crashes gRPC-Go xDS servers when the :authority and Host headers are absent. The vendor has not published proof-of-concept code or exploitation details for any of them, so the practical attack path into a given cluster depends on which KubeVirt endpoints an operator exposes.

KubeVirt is the layer that runs virtual machines as Kubernetes workloads, so these components form part of the cluster control plane rather than an isolated appliance. virt-api terminates HTTP/2 and gRPC traffic from the Kubernetes API server and from clients, virt-handler talks to every node agent, and the export proxy and export server are frequently reachable beyond the cluster boundary. An authorization bypass in that position erodes a trust boundary that operators assume holds, while the availability bugs translate into crashed or memory-starved control-plane pods and stalled virtual machine lifecycle operations for tenants that depend on them. Current exploitation signals remain low: FIRST EPSS places the thirty-day exploitation probability at 0.3 percent for CVE-2026-84303, 0.6 percent for CVE-2026-84304 and CVE-2026-84445, 0.4 percent for CVE-2026-56854 and CVE-2026-78662, 0.5 percent for CVE-2026-56855 and CVE-2026-78660, 0.9 percent for CVE-2026-78659 and CVE-2026-78663, 0.8 percent for CVE-2026-78669, and 0.7 percent for CVE-2026-97032. The same release also folds in operational fixes that matter to large virtualization estates, including a backport that stops virt-handler from undefining a Shutoff domain when QEMU startup outlasts the SyncVMI gRPC timeout on large-memory VFIO virtual machines, a change that passes the NOWAIT flag so stats collection no longer blocks on libvirt's domain job lock during migrations, and the shipping of testing manifests in the virt-tests subpackage on SUSE Linux.

Attack Surface

Cloud Service, Infrastructure, Supply Chain (Third-party vendors), Server OS

Tactics

Initial Access, Defense Evasion, Impact

Techniques

  • T1190 – Exploit Public-Facing Application
  • T1499 – Endpoint Denial of Service
  • T1499.004 – Application or System Exploitation
  • T1078 – Valid Accounts

SuperPRO's Threat Countermeasures Procedures

  1. Install the openSUSE Leap 16.0 patch with zypper in -t patch openSUSE-Leap-16.0-2081=1, bringing every kubevirt1.8 package to 1.8.4-160000.3.1. Clusters whose virt-api, virt-exportproxy or virt-exportserver endpoints are reachable from outside the cluster network should be done within the current week; fully internal clusters can take the next scheduled maintenance window.
  2. Verify the result with rpm -q kubevirt1.8-virt-api kubevirt1.8-virt-controller kubevirt1.8-virt-handler kubevirt1.8-virt-launcher kubevirt1.8-virt-operator and confirm the output reads 1.8.4-160000.3.1, then roll the virt-operator managed deployments and DaemonSets so running pods execute the rebuilt binaries rather than the cached image.
  3. Inventory any gRPC xDS RBAC HTTP filter policies that match on HTTP header names in these clusters; CVE-2026-84303 lets mixed-case or canonical-case header matches bypass them, so those policies cannot be treated as enforcing until the components rebuilt against the fixed google.golang.org/grpc are running.
  4. Restrict network reachability of virt-api, virt-exportproxy and virt-exportserver to the cluster and management networks using NetworkPolicy or upstream firewall rules, since the HTTP/2 flaws CVE-2026-78659, CVE-2026-78663, CVE-2026-84304, CVE-2026-84445 and CVE-2026-97032 are all unauthenticated and reachable by anything that can open an HTTP/2 or gRPC connection.
  5. Alert on OOMKilled terminations, CrashLoopBackOff states and unexplained restarts of virt-api, virt-handler and virt-exportserver pods, and on sustained CPU saturation in those containers, as these are the observable outcomes of the memory-exhaustion, HPACK race and missing :authority header crash conditions.
  6. Scan the kubevirt1.8 container-disk and sidecar-shim images with govulncheck or an SBOM scanner for golang.org/x/crypto/ssh, golang.org/x/net/http2 and google.golang.org/grpc module versions predating this update, so locally built or mirrored images are not left behind after the host packages are patched.
  7. After the update, confirm that large-memory VFIO virtual machines no longer fail hotplug with libvirt error 55 and that stats polling of migrating VMs stops logging 'cannot acquire state change lock', which validates the backported virt-handler SyncVMI timeout fix (upstream PR 18545, commit b98490cd81) and the NOWAIT stats change (release-1.8 commit 4f7eca22df).

Source

Code Red Cyber / VTA – coderedcyber.ai