# PyJWT accepts public JWK containers as HMAC secrets

Advisory record · `GHSA-w2cx-738m-mc7w`

- **Identifiers:** `GHSA-w2cx-738m-mc7w` · `CVE-2026-102273` · `PYSEC-2026-4151`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-347](https://cwe.mitre.org/data/definitions/347.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 29 Sept 2026
- **Updated:** 1 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 29 Sept 2026, 23:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pyjwt` (PyPI): affected `>=2.13.0, <2.14.0`; fixed in `2.14.0`

## Machine-written summary

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

> PyJWT versions 2.13.0 up to but not including 2.14.0 accept a public RSA, EC, or OKP key wrapped in a JWKS object, array, or similar container as an HMAC secret. An attacker who knows the public key can forge HS256, HS384, or HS512 tokens only if the application allows both HMAC and asymmetric algorithms and passes the same raw public JWK JSON as both the key and the HMAC secret. Upgrade to PyJWT 2.14.0, which contains the fix.

Written 1 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.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0018, the 6th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:09 UTC: First seen by agentprime
- 31 Oct 2026, 14:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w2cx-738m-mc7w)

## Sources

- [GitHub Advisory Database: GHSA-w2cx-738m-mc7w](https://github.com/advisories/GHSA-w2cx-738m-mc7w)
- [OSV: GHSA-w2cx-738m-mc7w](https://osv.dev/vulnerability/GHSA-w2cx-738m-mc7w)
- <https://github.com/jpadilla/pyjwt/security/advisories/GHSA-w2cx-738m-mc7w>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-102273>
- <https://github.com/jpadilla/pyjwt/commit/801cd128528c62d9b23fcd161d1a2e1c17982f95>
- <https://github.com/jpadilla/pyjwt>
- <https://github.com/jpadilla/pyjwt/releases/tag/2.14.0>

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-w2cx-738m-mc7w>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w2cx-738m-mc7w/>. Everything for agents: <https://agentprime.io/llms.txt>.