mcp-proxy · PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgery
Affects mcp-proxySource GCVE Database
CVSS 7.4 High : upgrade to 0.12.0_5 soon.
Data as of 30 Oct 2026, 08:29 UTC
- Patch
- Available – fixed in 0.12.0_5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NWhat to do
Upgrade mcp-proxy to 0.12.0_5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewmcp-proxypkg:brew/mcp-proxyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade PyJWT to version 0.12.0_5 or later where this issue is fixed. Avoid using JWKs with empty 'k' values in oct keys. If upgrading is not immediately possible, ensure that the JWKS used for verification does not contain empty keys. The vulnerability is patched in the stated fixed version.
Description
PyJWT versions up to 2.13.0 and the current master branch contain a vulnerability where the HMAC verification accepts an empty key when using JWKs with an oct key type and an empty 'k' value. This allows an attacker to forge tokens without knowledge of a secret if the application verifies tokens using such a JWK. The issue arises because the empty key rejection implemented for string/bytes secrets was not applied to the JWK verification path. This flaw is fixed in PyJWT version 0.12.0_5.