rpm package
opensuse/rclone&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/rclone&distro=openSUSE%20Tumbleweed
Vulnerabilities (79)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-97032 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | 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 of a response sent to | |
| CVE-2026-97031 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory ampli | |
| CVE-2026-97030 | Med | 6.1 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped. | |
| CVE-2026-94448 | Med | 6.1 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression lit | |
| CVE-2026-94447 | Hig | 7.8 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the user chooses to use can bypass the intended checksum. We now ensure that golang.org/toolchain always goes to the network fo | |
| CVE-2026-94444 | Hig | 7.8 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips14 | |
| CVE-2026-94440 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes. | |
| CVE-2026-94439 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tun | |
| CVE-2026-78669 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | 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. | |
| CVE-2026-78667 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU. | |
| CVE-2026-78663 | Cri | 9.1 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | 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 can exploit this to | |
| CVE-2026-78660 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | 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 headers to an HTTP/1 client | |
| CVE-2026-78659 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | 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 malicious client can exploit | |
| CVE-2026-56866 | Hig | 7.5 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connecti | |
| CVE-2026-56857 | Cri | 9.8 | < 1.75.2-1.1 | 1.75.2-1.1 | Oct 8, 2026 | On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is | |
| CVE-2026-84445 | Hig | — | < 1.75.2-1.1 | 1.75.2-1.1 | Sep 14, 2026 | gRPC-Go is the Go language implementation of gRPC. Prior to 1.82.2 and 1.83.2, servers created with xds.NewGRPCServer() allow internal/transport/http2_server.go to accept an RPC containing neither the :authority header nor the Host header, while RouteAndProcess in internal/xds/se | |
| CVE-2026-78662 | Hig | 7.5 | < 1.75.1-1.1 | 1.75.1-1.1 | Sep 2, 2026 | Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such | |
| CVE-2026-56855 | Hig | 7.5 | < 1.75.1-1.1 | 1.75.1-1.1 | Sep 2, 2026 | Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and t | |
| CVE-2026-56854 | Hig | 7.5 | < 1.75.1-1.1 | 1.75.1-1.1 | Aug 28, 2026 | The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCallback, KeyboardInteractiveCal | |
| CVE-2026-46603 | Hig | 7.5 | < 1.75.1-1.1 | 1.75.1-1.1 | Aug 14, 2026 | VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion. |
- affected < 1.75.2-1.1fixed 1.75.2-1.1
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 of a response sent to
- affected < 1.75.2-1.1fixed 1.75.2-1.1
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory ampli
- affected < 1.75.2-1.1fixed 1.75.2-1.1
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
- affected < 1.75.2-1.1fixed 1.75.2-1.1
When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression lit
- affected < 1.75.2-1.1fixed 1.75.2-1.1
Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY the user chooses to use can bypass the intended checksum. We now ensure that golang.org/toolchain always goes to the network fo
- affected < 1.75.2-1.1fixed 1.75.2-1.1
Previously, a user operating inside of a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY the user chooses to connect to can serve an arbitrary module in its place. We now unpack the trusted ziphash for the bundled golang.org/fips14
- affected < 1.75.2-1.1fixed 1.75.2-1.1
Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.
- affected < 1.75.2-1.1fixed 1.75.2-1.1
When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tun
- affected < 1.75.2-1.1fixed 1.75.2-1.1
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.
- affected < 1.75.2-1.1fixed 1.75.2-1.1
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.
- affected < 1.75.2-1.1fixed 1.75.2-1.1
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 can exploit this to
- affected < 1.75.2-1.1fixed 1.75.2-1.1
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 headers to an HTTP/1 client
- affected < 1.75.2-1.1fixed 1.75.2-1.1
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 malicious client can exploit
- affected < 1.75.2-1.1fixed 1.75.2-1.1
When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connecti
- affected < 1.75.2-1.1fixed 1.75.2-1.1
On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is
- affected < 1.75.2-1.1fixed 1.75.2-1.1
gRPC-Go is the Go language implementation of gRPC. Prior to 1.82.2 and 1.83.2, servers created with xds.NewGRPCServer() allow internal/transport/http2_server.go to accept an RPC containing neither the :authority header nor the Host header, while RouteAndProcess in internal/xds/se
- affected < 1.75.1-1.1fixed 1.75.1-1.1
Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such
- affected < 1.75.1-1.1fixed 1.75.1-1.1
Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. Now, we handle all RFC 4254 channel messages; global requests are handled explicitly. Then, treat all other messages as a protocol error and t
- affected < 1.75.1-1.1fixed 1.75.1-1.1
The source-address critical option in the Permissions returned by an authentication callback was only enforced for the PublicKeyCallback and VerifiedPublicKeyCallback paths, extending the fix for CVE-2026-46595. Permissions returned by the PasswordCallback, KeyboardInteractiveCal
- affected < 1.75.1-1.1fixed 1.75.1-1.1
VP8L decoding in golang.org/x/image/vp8l can allocate an excessive amount of memory when processing a crafted VP8L image containing many unused Huffman tree groups. This allows a remote attacker to cause a denial of service via memory exhaustion.
Page 1 of 4