https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:54:43 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-00111 bdu:2026-00111 https://cve.radiocsirt.org/vuln/bdu:2026-00111 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0315 certfr-2026-avi-0315 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0315 https://cve.radiocsirt.org/vuln/cleanstart-2026-ap81168 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: harbor-fips</p> <p>Multiple security vulnerabilities affect the harbor-fips package. These issues are resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: harbor-fips</p> <p>Multiple security vulnerabilities affect the harbor-fips package. These issues are resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-ap81168 https://cve.radiocsirt.org/vuln/euvd-2026-363320 EUVD-2026-363320 https://cve.radiocsirt.org/vuln/euvd-2026-363320 https://cve.radiocsirt.org/vuln/fkie_cve-2025-29923 <p>go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.2, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.2; however, 9.7.2 has been yanked and 9.7.3 is the lowest available patched version on the 9.7.x branch. As a workaround, set the flag `DisableIndentity` to `true` when constructing the client instance.</p> <p>go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.2, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.2; however, 9.7.2 has been yanked and 9.7.3 is the lowest available patched version on the 9.7.x branch. As a workaround, set the flag `DisableIndentity` to `true` when constructing the client instance.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-29923 https://cve.radiocsirt.org/vuln/ghsa-92cp-5422-2mw7 <p><strong>Affected:</strong> Go: github.com/redis/go-redis/v9</p> <p>### Impact</p> <p>The issue only occurs when the `CLIENT SETINFO` command times out during connection establishment. The following circumstances can cause such a timeout:</p> <p>1. The client is configured to transmit its identity. This can be disabled via the `DisableIndentity` flag. 2. There are network connectivity issues 3. The client was configured with aggressive timeouts</p> <p>The impact differs by use case:</p> <p>* **Sticky connections**: Rather than using a connection from the pool on-demand, the caller can stick with a connection. Then you receive persistent out-of-order responses for the lifetime of the connection. * **Pipelines**: All commands in the pipeline receive incorrect responses. * **Default connection pool usage without pipelining**: When used with the default [ConnPool](https://github.com/redis/go-redis/blob/8fadbef84a3f4e7573f8b38e5023fd469470a8a4/internal/pool/pool.go#L77) once a connection is returned after use with [ConnPool#Put](https://github.com/redis/go-redis/blob/8fadbef84a3f4e7573f8b38e5023fd469470a8a4/internal/pool/pool.go#L366) the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded.</p> <p>### Patches We prepared a fix in https://github.com/redis/go-redis/pull/3295 and plan to release patch versions soon. Versions 9.7.2, 9.6.3, and 9.5.5 were patched. However, 9.7.2 has been yanked, making 9.7.3 the lowest available 9.7.x version with a patch.…</p> <p><strong>Affected:</strong> Go: github.com/redis/go-redis/v9</p> <p>### Impact</p> <p>The issue only occurs when the `CLIENT SETINFO` command times out during connection establishment. The following circumstances can cause such a timeout:</p> <p>1. The client is configured to transmit its identity. This can be disabled via the `DisableIndentity` flag. 2. There are network connectivity issues 3. The client was configured with aggressive timeouts</p> <p>The impact differs by use case:</p> <p>* **Sticky connections**: Rather than using a connection from the pool on-demand, the caller can stick with a connection. Then you receive persistent out-of-order responses for the lifetime of the connection. * **Pipelines**: All commands in the pipeline receive incorrect responses. * **Default connection pool usage without pipelining**: When used with the default [ConnPool](https://github.com/redis/go-redis/blob/8fadbef84a3f4e7573f8b38e5023fd469470a8a4/internal/pool/pool.go#L77) once a connection is returned after use with [ConnPool#Put](https://github.com/redis/go-redis/blob/8fadbef84a3f4e7573f8b38e5023fd469470a8a4/internal/pool/pool.go#L366) the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded.</p> <p>### Patches We prepared a fix in https://github.com/redis/go-redis/pull/3295 and plan to release patch versions soon. Versions 9.7.2, 9.6.3, and 9.5.5 were patched. However, 9.7.2 has been yanked, making 9.7.3 the lowest available 9.7.x version with a patch.…</p> https://cve.radiocsirt.org/vuln/ghsa-92cp-5422-2mw7 https://cve.radiocsirt.org/vuln/msrc_cve-2025-29923 msrc_CVE-2025-29923 https://cve.radiocsirt.org/vuln/msrc_cve-2025-29923 https://cve.radiocsirt.org/vuln/opensuse-su-2025:14937-1 <p>govulncheck-vulndb-0.0.20250327T184518-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20250327T184518-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:14937-1 https://cve.radiocsirt.org/vuln/suse-su-2025:01987-1 <p>Security update for Multi-Linux Manager Client Tools</p> <p>Security update for Multi-Linux Manager Client Tools</p> https://cve.radiocsirt.org/vuln/suse-su-2025:01987-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-29923 <p><strong>Affected:</strong> Ubuntu:18.04:LTS: golang-github-go-redis-redis, Ubuntu:20.04:LTS: golang-github-go-redis-redis, Ubuntu:22.04:LTS: golang-github-go-redis-redis, Ubuntu:24.04:LTS: golang-github-go-redis-redis, Ubuntu:25.10: golang-github-go-redis-redis, Ubuntu:26.04:LTS: golang-github-go-redis-redis</p> <p>go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.2, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.2; however, 9.7.2 has been yanked and 9.7.3 is the lowest available patched version on the 9.7.x branch. As a workaround, set the flag `DisableIndentity` to `true` when constructing the client instance.</p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: golang-github-go-redis-redis, Ubuntu:20.04:LTS: golang-github-go-redis-redis, Ubuntu:22.04:LTS: golang-github-go-redis-redis, Ubuntu:24.04:LTS: golang-github-go-redis-redis, Ubuntu:25.10: golang-github-go-redis-redis, Ubuntu:26.04:LTS: golang-github-go-redis-redis</p> <p>go-redis is the official Redis client library for the Go programming language. Prior to 9.5.5, 9.6.3, and 9.7.2, go-redis potentially responds out of order when `CLIENT SETINFO` times out during connection establishment. This can happen when the client is configured to transmit its identity, there are network connectivity issues, or the client was configured with aggressive timeouts. The problem occurs for multiple use cases. For sticky connections, you receive persistent out-of-order responses for the lifetime of the connection. All commands in the pipeline receive incorrect responses. When used with the default ConnPool once a connection is returned after use with ConnPool#Put the read buffer will be checked and the connection will be marked as bad due to the unread data. This means that at most one out-of-order response before the connection is discarded. This issue is fixed in 9.5.5, 9.6.3, and 9.7.2; however, 9.7.2 has been yanked and 9.7.3 is the lowest available patched version on the 9.7.x branch. As a workaround, set the flag `DisableIndentity` to `true` when constructing the client instance.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-29923 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0633 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um Daten zu manipulieren, oder einen Denial of Service auszulösen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um Daten zu manipulieren, oder einen Denial of Service auszulösen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0633