CVE-2024-37568
Authlib vulnerability
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.)
Affected products
Authlib. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Authlib runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- nvd.nist.gov/vuln/detail/CVE-2024-37568
- github.com/lepture/authlib/issues/654
- github.com/pypa/advisory-database/tree/main/vulns/authlib/PYSEC-2024-52.yaml
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/I
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F
- www.vicarius.io/vsociety/posts/algorithm-confusion-in-lepture-authlib-cve-2024-37568
- lists.debian.org/debian-lts-announce/2025/10/msg00032.html
- github.com/advisories/GHSA-5357-c2jx-v7qh
- nvd.nist.gov/vuln/detail/CVE-2024-37568
- cve.org/CVERecord?id=CVE-2024-37568
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.