https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 13:06:12 +0000 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0214 certfr-2025-avi-0214 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0214 https://cve.radiocsirt.org/vuln/cleanstart-2026-aq94704 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: minio-operator</p> <p>Multiple security vulnerabilities affect the minio-operator package. Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: minio-operator</p> <p>Multiple security vulnerabilities affect the minio-operator package. Previously, after a channel has been established, a malicious peer could send crafted messages that would deadlock the entire connection. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-aq94704 https://cve.radiocsirt.org/vuln/euvd-2026-199336 EUVD-2026-199336 https://cve.radiocsirt.org/vuln/euvd-2026-199336 https://cve.radiocsirt.org/vuln/fkie_cve-2024-51744 <p>golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in &#34;dangerous&#34; situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors (&#34;dangerous&#34; ones first), so that you are not running in the case detailed above.</p> <p>golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in &#34;dangerous&#34; situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors (&#34;dangerous&#34; ones first), so that you are not running in the case detailed above.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-51744 https://cve.radiocsirt.org/vuln/ghsa-29wx-vh33-7x7r <p><strong>Affected:</strong> Go: github.com/golang-jwt/jwt/v4</p> <p>### Summary</p> <p>Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens.</p> <p>### Fix</p> <p>We have back-ported the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in &#34;dangerous&#34; situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release.</p> <p>### Workaround</p> <p>We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors (&#34;dangerous&#34; ones first), so that you are not running in the case detailed above.</p> <p>```Go token, err := /* jwt.Parse or similar */ if token.Valid { fmt.Println(&#34;You look nice today&#34;) } else if errors.Is(err, jwt.ErrTokenMalformed) { fmt.Println(&#34;That&#39;s not even a token&#34;) } else if errors.Is(err, jwt.ErrTokenUnv…</p> <p><strong>Affected:</strong> Go: github.com/golang-jwt/jwt/v4</p> <p>### Summary</p> <p>Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens.</p> <p>### Fix</p> <p>We have back-ported the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in &#34;dangerous&#34; situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release.</p> <p>### Workaround</p> <p>We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors (&#34;dangerous&#34; ones first), so that you are not running in the case detailed above.</p> <p>```Go token, err := /* jwt.Parse or similar */ if token.Valid { fmt.Println(&#34;You look nice today&#34;) } else if errors.Is(err, jwt.ErrTokenMalformed) { fmt.Println(&#34;That&#39;s not even a token&#34;) } else if errors.Is(err, jwt.ErrTokenUnv…</p> https://cve.radiocsirt.org/vuln/ghsa-29wx-vh33-7x7r https://cve.radiocsirt.org/vuln/msrc_cve-2024-51744 msrc_CVE-2024-51744 https://cve.radiocsirt.org/vuln/msrc_cve-2024-51744 https://cve.radiocsirt.org/vuln/opensuse-su-2024:14484-1 <p>govulncheck-vulndb-0.0.20241112T145010-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20241112T145010-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14484-1 https://cve.radiocsirt.org/vuln/rhsa-2025:11351 <p>golang-jwt: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt golang.org/x/oauth2/jws: Unexpected memory consumption during token parsing in golang.org/x/oauth2/jws</p> <p>golang-jwt: Bad documentation of error handling in ParseWithClaims can lead to potentially dangerous situations in golang-jwt golang.org/x/oauth2/jws: Unexpected memory consumption during token parsing in golang.org/x/oauth2/jws</p> https://cve.radiocsirt.org/vuln/rhsa-2025:11351 https://cve.radiocsirt.org/vuln/suse-su-2024:4042-1 <p>Security update for govulncheck-vulndb</p> <p>Security update for govulncheck-vulndb</p> https://cve.radiocsirt.org/vuln/suse-su-2024:4042-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-51744 <p><strong>Affected:</strong> Ubuntu:22.04:LTS: golang-github-golang-jwt-jwt, Ubuntu:24.04:LTS: golang-github-golang-jwt-jwt, Ubuntu:24.04:LTS: golang-github-golang-jwt-jwt-v5, Ubuntu:25.10: golang-github-golang-jwt-jwt, Ubuntu:25.10: golang-github-golang-jwt-jwt-v5, Ubuntu:26.04:LTS: golang-github-golang-jwt-jwt, Ubuntu:26.04:LTS: golang-github-golang-jwt-jwt-v5</p> <p>golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in &#34;dangerous&#34; situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors (&#34;dangerous&#34; ones first), so that you are not running in the case detailed above.</p> <p><strong>Affected:</strong> Ubuntu:22.04:LTS: golang-github-golang-jwt-jwt, Ubuntu:24.04:LTS: golang-github-golang-jwt-jwt, Ubuntu:24.04:LTS: golang-github-golang-jwt-jwt-v5, Ubuntu:25.10: golang-github-golang-jwt-jwt, Ubuntu:25.10: golang-github-golang-jwt-jwt-v5, Ubuntu:26.04:LTS: golang-github-golang-jwt-jwt, Ubuntu:26.04:LTS: golang-github-golang-jwt-jwt-v5</p> <p>golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in &#34;dangerous&#34; situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors (&#34;dangerous&#34; ones first), so that you are not running in the case detailed above.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-51744