Skip to main content
EPSS 0.2%top 88%

CVE-2026-85394: Improper Verification of Cryptographic Signature in mpdavis python-jose

0
Critical
Published: 09/03/2026 (09/03/2026, 18:54:26 UTC)
Source: CVE Database V5
Vendor/Project: mpdavis
Product: python-jose

Description

python-jose through 3.5.0 fails to properly validate asymmetric keys in HMAC initialization, accepting DER-encoded public keys that lack PEM armor or SSH prefixes. Attackers holding the service's public key can forge HS256 tokens that pass verification when algorithms are not explicitly restricted. This is an incomplete fix for CVE-2024-33663.

CVSS v4.0

Score 9.3critical

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
High
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Affected software

mpdavis

python-jose

Affected versions
>=0 <=3.5.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/14/2026, 23:27:36 UTC

Technical Analysis

The vulnerability in python-jose (up to version 3.5.0) involves improper verification of cryptographic signatures due to acceptance of DER-encoded public keys lacking expected PEM or SSH formatting during HMAC initialization. This flaw enables an attacker who possesses the service's public key to forge HS256 tokens that can bypass signature verification when the application does not explicitly restrict accepted algorithms. This vulnerability is an incomplete remediation of CVE-2024-33663 and carries a CVSS 4.0 base score of 9.3, indicating critical severity.

Potential Impact

An attacker with access to the service's public key can forge HS256 tokens that will be accepted as valid by the vulnerable python-jose library, potentially allowing unauthorized access or privilege escalation in applications relying on this token verification. The vulnerability affects the cryptographic trust model by undermining signature validation, which can lead to token forgery and bypass of authentication or authorization controls.

Mitigation Recommendations

No explicit patch or fix link is provided in the available data. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. In the meantime, applications should explicitly restrict accepted algorithms to prevent acceptance of forged tokens. Monitoring vendor advisories for an official fix is recommended.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulnCheck
Date Reserved
2026-09-03T18:10:58.475Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a99c5a7acd9273b4957e1ed

Added to database: 09/03/2026, 19:08:23 UTC

Last enriched: 09/14/2026, 23:27:36 UTC

Last updated: 10/17/2026, 18:48:23 UTC

Views: 89

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses