CVE-2024-37568 · cross-distro fix matrix

CVE-2024-37568: 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.)

Affects 2 Linux releases across 2 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2024-37568 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

python-authlib→ fixed in0.15.4-1+deb11u1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-authlib
```

Debian trixie

Source: Debian Security Tracker

python-authlib→ fixed in1.3.1-1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y python-authlib
```

Are YOU affected by CVE-2024-37568?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2024-37568dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)