Quick answers
- Is CVE-2026-85394 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85394 being exploited in the wild.
- How severe is CVE-2026-85394?
- Critical severity, with a CVSS score of 9.1, published 3 September 2026.
- Which products and versions are affected?
- python-jose (PyPI) <= 3.5.0.
- Is there a fix for CVE-2026-85394?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85394 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85394?
- Check whether you run python-jose (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
python-jose fails to properly validate key formats during HMAC (HS256) initialization, accepting DER-encoded public keys that lack PEM armor or SSH prefixes. An attacker with knowledge of a service's public key (often publicly available) can construct and sign tokens using the HMAC algorithm, bypassing asymmetric signature verification when explicit algorithm restrictions are not enforced. The vulnerability is an incomplete fix for CVE-2024-33663, which addressed similar algorithm confusion with OpenSSH ECDSA keys. No authentication or user interaction is required; exploitation requires only network access to a service using the vulnerable library. Patched versions enforce stricter key format validation to prevent key confusion between asymmetric and symmetric algorithms.
Affected products
- python-jose python-jose through 3.5.0
Identifiers
- CVE-2026-85394
- GHSA-3qf3-8w2g-rqmx
Timeline
- 2026-09-03: disclosed
- other: Related to incomplete fix for CVE-2024-33663 (prior algorithm confusion vulnerability)