SUSE · Security update for kubevirt1.8
Affects SUSESource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.5 High : upgrade SUSE ssh to 0.55.0 soon.
Data as of 18 Nov 2026, 15:19 UTC
- Patch
- Available – fixed in 0.55.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade golang.org/x/crypto/ssh to 0.55.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/cryptogolang.org/x/crypto/ssh | Affected
| Fixed in
|
Gogolang.org/x/crypto/sshpkg:golang/golang.org/x/crypto/sshOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
This update for kubevirt1.8 fixes the following issues: - CVE-2026-56854,CVE-2026-56855,CVE-2026-78662: golang.org/x/crypto/ssh: authentication bypass and deadlocks in the `crypto/ssh` library (bsc#1278574). - CVE-2026-78659: golang.org/x/net/http2: HTTP/2 server memory exhaustion due to `Trailer` headers (bsc#1286984). - CVE-2026-78660: golang.org/x/net/http2: HTTP/2 transport accepts malformed framing-related headers (bsc#1287039). - CVE-2026-78663: golang.org/x/net/http2: double flow control refund on HTTP/2 server streams (bsc#1287143). - CVE-2026-78669: golang.org/x/net/http2: excessive CPU consumption from repeated initial window changes (bsc#1285255). - CVE-2026-84303: google.golang.org/grpc: xDS RBAC HTTP filter implementation issue allows for bypass of authorization policies via mixed-case or canonical-case header matches (bsc#1279276). - CVE-2026-84304: google.golang.org/grpc: heap memory exhaustion via HTTP/2 `DATA` frame fragmentation (bsc#1279184). - CVE-2026-84445: google.golang.org/grpc: DoS via crash due to missing `:authority` and 'Host' headers in gRPC-Go xDS servers (bsc#1278869). - CVE-2026-97032: golang.org/x/net/http2: HTTP/2 server crash due to `HPACK` encoder race (bsc#1287446). Changes for kubevirt1.8: - Backport the slow qemu startup fix for virt-handler: when qemu took longer to start than the SyncVMI gRPC timeout, as large-memory VFIO VMs do, virt-handler undefined the Shutoff domain of a Scheduled VMI while startup was still running. The VM then ran as a transient domain and later hotplug failed with libvirt error 55. Defer the deletion for up to 5 minutes (upstream PR 18545, commit b98490cd81). - Build with Go 1.26: the updated modules require it (go.mod) - virt-launcher's domain stats collection took libvirt's domain job lock, which an in-flight migration holds on the target, so every stats poll of a migrating VM blocked for the 30 s job timeout and logged "cannot acquire state change lock". Pass the NOWAIT flag so libvirt skips the locked domain instead (upstream release-1.8 commit 4f7eca22df). - Ship the testing manifests in the tests subpackage on SUSE Linux: they were generated and installed only on Tumbleweed, together with the release manifests, so virt-tests came without the default-config.json, rbac-for-testing.yaml, uploadproxy-nodeport.yaml and disks-images-provider.yaml it needs to run. The release manifests and the manifests subpackage stay Tumbleweed-only.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2026/opensuse-su-2026_22331-1.json (opens in a new tab)
- bugzilla.suse.com/1278574 (opens in a new tab)
- bugzilla.suse.com/1278869 (opens in a new tab)
- bugzilla.suse.com/1279184 (opens in a new tab)
- bugzilla.suse.com/1279276 (opens in a new tab)
- bugzilla.suse.com/1285255 (opens in a new tab)
- bugzilla.suse.com/1286984 (opens in a new tab)
- bugzilla.suse.com/1287039 (opens in a new tab)
- bugzilla.suse.com/1287143 (opens in a new tab)
- bugzilla.suse.com/1287446 (opens in a new tab)
- suse.com/security/cve/CVE-2026-56854/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-56855/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-78659/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-78660/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-78662/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-78663/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-78669/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-84303/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-84304/ (opens in a new tab)