CVE-2024-37568 — lepture Authlib before 1

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.)

01What is this 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.)

02Affected products

Vendor	Product	Versions
n	a / n/a	n/a

03Active exploitation status

Not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog. EPSS is the best forward-looking signal — see the EPSS row above.

04Recommended remediation

• Patch to a fixed version listed in the vendor advisory (see references below).
• Mitigate with WAF rules, network egress filters, or feature flags where the patch is not yet available.
• Hunt historical logs for exploitation indicators — see Detection signatures below.

05Technical details

For the full vendor write-up, exploit chains, and reference implementations, see the references list in section 09.

06Detection signatures

Open the Sigma generator with a pre-filled prompt for this CVE to draft a starting detection in your stack of choice:

Open in Sigma generator →

07Related CVEs

08Timeline

• Published: 2024-06-09T00:00:00.000Z
• Last modified: 2025-11-03T17:31:16.986Z

09References

• github.com — https://github.com/lepture/authlib/issues/654
• lists.fedoraproject.org — https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedorapro…
• lists.fedoraproject.org — https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedorapro…
• www.vicarius.io — https://www.vicarius.io/vsociety/posts/algorithm-confusion-in-lepture-authlib-cv…