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

Advisory record · `GHSA-5357-c2jx-v7qh`

- **Identifiers:** `GHSA-5357-c2jx-v7qh` · `CVE-2024-37568` · `PYSEC-2024-52`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 9 Jun 2024
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Jun 2024, 19:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `authlib` (PyPI): affected `<1.3.1`; fixed in `1.3.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Authlib versions before 1.3.1 are vulnerable to algorithm confusion when verifying JSON Web Tokens with asymmetric public keys. If the algorithm is not specified in a jwt.decode call, HMAC verification is accepted using the public key, so an attacker who can present a crafted token may be able to forge tokens that pass verification. Upgrade authlib to version 1.3.1 or later. Until then, specify the expected algorithm explicitly in every jwt.decode call.

Written 10 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from ADP (CISA-ADP)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 9 Jun 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-5357-c2jx-v7qh](https://github.com/advisories/GHSA-5357-c2jx-v7qh)
- [OSV: GHSA-5357-c2jx-v7qh](https://osv.dev/vulnerability/GHSA-5357-c2jx-v7qh)
- <https://github.com/advisories/GHSA-5357-c2jx-v7qh>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5357-c2jx-v7qh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5357-c2jx-v7qh/>. Everything for agents: <https://agentprime.io/llms.txt>.
