Summary
This update for kubevirt1.9 fixes the following issues:
- CVE-2026-13622: virt-handler migration proxy follows symlinks allowing container escape to host (bsc#1272840).
- 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-97032: golang.org/x/net/http2: HTTP/2 server crash due to HPACK encoder race (bsc#1287446).
Update to version 1.9.1:
* virt-template is pinned at v0.2.3
* several bug fixes, see
https://github.com/kubevirt/kubevirt/releases/tag/v1.9.1
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 16.0 | kubevirt1.9 | 1.9.1-160000.1.1 |
Vulnerabilities 6
-
Critical 9.1
Double flow control refund on HTTP/2 server streams in net/http
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client…
-
High 8.8
Kubevirt: virt-handler-rhel9: kubevirt: virt-handler migration proxy follows symlinks allowing container escape to host
A symlink following vulnerability was found in KubeVirt's virt-handler migration proxy. During live migration, virt-handler dials Unix sockets inside the target virt-launcher pod via /proc/<pid>/root/ paths using net.Dial() without symlink protection. These s…
-
High 7.5
HTTP/2 server memory exhaustion due to Trailer headers in net/http
When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicio…
-
High 7.5
HTTP/2 transport accepts malformed framing-related headers in net/http
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such header…
-
High 7.5
Excessive CPU consumption from repeated initial window changes in net/http
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.
-
High 7.5
HTTP/2 server crash due to HPACK encoder race in net/http
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part …
References
-
report
https://bugzilla.suse.com/1272840
-
report
https://bugzilla.suse.com/1285255
-
report
https://bugzilla.suse.com/1286984
-
report
https://bugzilla.suse.com/1287039
-
report
https://bugzilla.suse.com/1287143
-
report
https://bugzilla.suse.com/1287446
-
web
https://www.suse.com/security/cve/CVE-2026-13622
-
web
https://www.suse.com/security/cve/CVE-2026-78659
-
web
https://www.suse.com/security/cve/CVE-2026-78660
-
web
https://www.suse.com/security/cve/CVE-2026-78663
-
web
https://www.suse.com/security/cve/CVE-2026-78669
-
web
https://www.suse.com/security/cve/CVE-2026-97032