In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does…
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- Partial Red Hat: 1 without a fix
Attack profile from CVSS 3.0 · NVD. Fix status from CNA, GitHub and Red Hat.
Summary
In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM encoded public keys. Specifically, the PKCS1 PEM encoded format would be allowed because it is prefaced with the string `-----BEGIN RSA PUBLIC KEY-----` which is not accounted for. This enables symmetric/asymmetric key confusion attacks against users using the PKCS1 PEM encoded public keys, which would allow an attacker to craft JWTs from scratch.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
| — | pyjwt (PyPI) | before 1.5.1 | 1.5.1 | Patch available | GHSA-r9jw-mwhq-wp62 |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
- pyjwt (PyPI) Vendor— Affected before 1.5.1 Fixed in 1.5.1 Patch available GHSA-r9jw-mwhq-wp62
Remediation
- Fix · GHSA-r9jw-mwhq-wp62 pyjwt (PyPI) Fixed in 1.5.1 Advisory →
Vendor assessments
Red Hat
Red Hat rating: Moderate. Red Hat's page for this CVE →
| Product | Status | Plan or fix |
|---|---|---|
| Red Hat Storage 3 | Affected | No fix planned: Will not fix |
Not affected: 1 product
- Red Hat Enterprise Linux 7
Timeline
- 2026-10-02 Threatist record created from CVE-2017-11424
- 2026-10-03 Alias added: GHSA-r9jw-mwhq-wp62
References
Sources
- CVE-2017-11424 · CVE Program
- CVE-2017-11424 · NVD
- FIRST EPSS
- GHSA-r9jw-mwhq-wp62 · GitHub Advisory Database · CC BY 4.0
- CVE-2017-11424 · Red Hat security data · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences