https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 18:35:12 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-257447 EUVD-2026-257447 https://cve.radiocsirt.org/vuln/euvd-2026-257447 https://cve.radiocsirt.org/vuln/fkie_cve-2024-37568 <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-37568 https://cve.radiocsirt.org/vuln/ghsa-5357-c2jx-v7qh <p><strong>Affected:</strong> PyPI: authlib</p> <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> <p><strong>Affected:</strong> PyPI: authlib</p> <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> https://cve.radiocsirt.org/vuln/ghsa-5357-c2jx-v7qh https://cve.radiocsirt.org/vuln/opensuse-su-2024:14035-1 <p>python310-Authlib-1.3.1-1.1 on GA media</p> <p>python310-Authlib-1.3.1-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2024:14035-1 https://cve.radiocsirt.org/vuln/pysec-2024-52 <p><strong>Affected:</strong> PyPI: authlib</p> <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> <p><strong>Affected:</strong> PyPI: authlib</p> <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> https://cve.radiocsirt.org/vuln/pysec-2024-52 https://cve.radiocsirt.org/vuln/suse-su-2024:2064-1 <p>Security update for python-Authlib</p> <p>Security update for python-Authlib</p> https://cve.radiocsirt.org/vuln/suse-su-2024:2064-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-37568 <p><strong>Affected:</strong> Ubuntu:Pro:22.04:LTS: python-authlib, Ubuntu:Pro:24.04:LTS: python-authlib, Ubuntu:25.10: python-authlib, Ubuntu:Pro:26.04:LTS: python-authlib</p> <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> <p><strong>Affected:</strong> Ubuntu:Pro:22.04:LTS: python-authlib, Ubuntu:Pro:24.04:LTS: python-authlib, Ubuntu:25.10: python-authlib, Ubuntu:Pro:26.04:LTS: python-authlib</p> <p>lepture Authlib before 1.3.1 has algorithm confusion with asymmetric public keys. Unless an algorithm is specified in a jwt.decode call, HMAC verification is allowed with any asymmetric public key. (This is similar to CVE-2022-29217 and CVE-2024-33663.)</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-37568