Cyber Resilience

CVE-2026-102268

Pyjwt Project Pyjwt ≤ 2.14.0

Public PoC
Published
28 September 2026
Modified
07 October 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0020 8th percentile
Risk Priority 65 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-102268 is a critical-severity Improper Verification of Cryptographic Signature (CWE-347) vulnerability in Pyjwt Project Pyjwt. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Invalid Code Signature (T1036.001); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, is_pem_format in jwt/utils.py is affected because is_pem_format does not recognize every PEM representation accepted by the cryptography loader. This occurs when an application mixes HMAC and asymmetric…

more

algorithms and supplies a mutated public-key PEM as raw key bytes. As a result, HMACAlgorithm.prepare_key treats the unrecognized asymmetric public key as an HMAC secret. Consequently, an attacker who knows the public key can forge authenticated HMAC tokens. This issue is fixed in version 2.14.0.

CWE(s)
CWE-347

Related Threats

MITRE ATT&CK Enterprise Techniques

T1036.001 Invalid Code Signature Stealth
Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool.
attack.mitre.org →
T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1542 Pre-OS Boot Stealth
Adversaries may abuse Pre-OS Boot mechanisms as a way to establish persistence on a system.
attack.mitre.org →
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
attack.mitre.org →
T1553.002 Code Signing Defense Impairment
Adversaries may create, acquire, or steal code signing materials to sign their malware or tools.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-41159Shared CWE-347
CVE-2026-13743Shared CWE-347
CVE-2024-6800Shared CWE-347
CVE-2026-91187Shared CWE-347
CVE-2026-102266Shared CWE-347
CVE-2024-51526Shared CWE-347
CVE-2025-20206Shared CWE-347
CVE-2023-42806Shared CWE-347
CVE-2026-0265Shared CWE-347
CVE-2024-37886Shared CWE-347

Affected Assets

pyjwt project
pyjwt
≤ 2.14.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 14 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection partial match

Requiring cryptographic protection mechanisms forces correct signature verification to be implemented for data protection.

SC-23 Session Authenticity partial match

Protecting session authenticity requires correct verification of cryptographic signatures or equivalent mechanisms.

SI-7 Software, Firmware, and Information Integrity partial match

Mandating integrity verification tools directly requires proper cryptographic signature checking to detect unauthorized changes.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-09 partial match
blocks

Requires assessing authenticity and integrity of acquired assets, which commonly relies on signature verification but is limited to pre-acquisition.

PR.DS-01 partial match
blocks

Digital signatures are explicitly cited to protect integrity of data-at-rest, so proper verification directly mitigates the weakness.

PR.DS-02 partial match
blocks

Digital signatures are explicitly cited to protect integrity of data-in-transit, so proper verification directly mitigates the weakness.

PR.PS-06 partial match
blocks

Secure SDLC practices include code signing and signature verification requirements, addressing the weakness during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.14 Information transfer partial match
removes
A.5.15 Access control partial match
removes
A.5.16 Identity management partial match
removes
A.5.17 Authentication information partial match
removes
A.5.18 Access rights partial match
removes
A.8.10 Information deletion partial match
removes

References