CVE-2026-102275: CWE-345: Insufficient Verification of Data Authenticity in jpadilla pyjwt
PyJWT versions from 2.1.0 up to but not including 2.15.0 contain a vulnerability in the OKPAlgorithm.from_jwk function where the private JWK import does not verify that the public key component x corresponds to the private key component d. This can lead to a mismatch between the identity derived from x and cryptographic operations performed with d. If an integration accepts private key parameters from a proof header without rejecting them, an attacker could misuse a stolen sender-constrained token without possessing the legitimate private key. The issue is fixed in version 2.15.0.
AI Analysis
Technical Summary
PyJWT, a Python library implementing JSON Web Token standards, has a vulnerability (CVE-2026-102275) affecting versions >=2.1.0 and <2.15.0. The flaw exists in the OKPAlgorithm.from_jwk function where the private JWK import path fails to verify that the public key component x matches the private key component d. This insufficient verification of data authenticity (CWE-345) can allow an attacker to use a stolen sender-constrained token without the legitimate private key if the integration accepts private key parameters from a proof header without rejection. The vulnerability is resolved in version 2.15.0.
Potential Impact
An attacker may exploit this vulnerability to use a stolen sender-constrained token without possessing the legitimate private key, potentially leading to unauthorized actions or identity misuse. The confidentiality impact is low, integrity impact is high, and availability is not affected. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade PyJWT to version 2.15.0 or later, where this vulnerability has been fixed. Until then, ensure that integrations do not accept private key parameters from proof headers without proper validation to prevent misuse.
CVE-2026-102275: CWE-345: Insufficient Verification of Data Authenticity in jpadilla pyjwt
Description
PyJWT versions from 2.1.0 up to but not including 2.15.0 contain a vulnerability in the OKPAlgorithm.from_jwk function where the private JWK import does not verify that the public key component x corresponds to the private key component d. This can lead to a mismatch between the identity derived from x and cryptographic operations performed with d. If an integration accepts private key parameters from a proof header without rejecting them, an attacker could misuse a stolen sender-constrained token without possessing the legitimate private key. The issue is fixed in version 2.15.0.
CVSS v3.1
Score 6.5medium
Affected software
jpadilla
pyjwt
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
PyJWT, a Python library implementing JSON Web Token standards, has a vulnerability (CVE-2026-102275) affecting versions >=2.1.0 and <2.15.0. The flaw exists in the OKPAlgorithm.from_jwk function where the private JWK import path fails to verify that the public key component x matches the private key component d. This insufficient verification of data authenticity (CWE-345) can allow an attacker to use a stolen sender-constrained token without the legitimate private key if the integration accepts private key parameters from a proof header without rejection. The vulnerability is resolved in version 2.15.0.
Potential Impact
An attacker may exploit this vulnerability to use a stolen sender-constrained token without possessing the legitimate private key, potentially leading to unauthorized actions or identity misuse. The confidentiality impact is low, integrity impact is high, and availability is not affected. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade PyJWT to version 2.15.0 or later, where this vulnerability has been fixed. Until then, ensure that integrations do not accept private key parameters from proof headers without proper validation to prevent misuse.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-28T20:11:16.658Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6abad639f7a7c54106343f76
Added to database: 09/28/2026, 21:03:53 UTC
Last enriched: 09/28/2026, 21:17:46 UTC
Last updated: 09/28/2026, 21:19:28 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.