# PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion

Advisory record · `GHSA-x33g-cr3x-6449`

- **Identifiers:** `GHSA-x33g-cr3x-6449` · `CVE-2026-102275` · `PYSEC-2026-4183`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-345](https://cwe.mitre.org/data/definitions/345.html) · [CWE-348](https://cwe.mitre.org/data/definitions/348.html)
- **Tags:** [CWE-345](https://agentprime.io/advisories/tag/cwe-345.md) · [CWE-348](https://agentprime.io/advisories/tag/cwe-348.md)
- **Published:** 5 Oct 2026
- **Updated:** 7 Oct 2026
- **Reviewed by a person:** No

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

## Affected packages

- `pyjwt` (PyPI): affected `>=2.1.0, <2.15.0`; fixed in `2.15.0`

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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N`, from CNA (GitHub_M)

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

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x33g-cr3x-6449)

## Sources

- [GitHub Advisory Database: GHSA-x33g-cr3x-6449](https://github.com/advisories/GHSA-x33g-cr3x-6449)
- [OSV: GHSA-x33g-cr3x-6449](https://osv.dev/vulnerability/GHSA-x33g-cr3x-6449)
- <https://github.com/jpadilla/pyjwt/security/advisories/GHSA-x33g-cr3x-6449>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-102275>
- <https://github.com/jpadilla/pyjwt/commit/3cd9ceec33ced359decbad75b413ad668ae6332c>
- <https://github.com/jpadilla/pyjwt>
- <https://github.com/jpadilla/pyjwt/releases/tag/2.15.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-x33g-cr3x-6449>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x33g-cr3x-6449/>. Everything for agents: <https://agentprime.io/llms.txt>.