CVE-2026-102270: PyJWT: ReDoS vulnerability when calling the `is_pem_format` function.
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: jpadilla pyjwt 2.14.0; azl3 python-jwt 2.13.0-1 on Azure Linux 3.0 2.15.1-1.
Low priority for now. Upgrade to jpadilla pyjwt 2.14.0; azl3 python-jwt 2.13.0-1 on Azure Linux 3.0 2.15.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT is_pem_format is affected because lazy PEM regular expression backtracks extensively. This occurs when a certificate-like input contains repeated BEGIN markers without a matching END marker. As a result, is_pem_format performs unbounded backtracking while searching for a PEM end marker. Consequently, an attacker can cause intensive CPU consumption. This issue is fixed in version 2.14.0.
- Published
- Sep 28, 2026
- Updated
- Oct 6, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-1333
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.9
- CNA · GitHub_M
- 4.4
- 0.5 point gap
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pyjwt project | pyjwt | cpe:2.3:a:pyjwt_project:pyjwt |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
jpadilla pyjwt
- < 2.14.0affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pyjwt project pyjwtbefore 2.14.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pyjwt | from 0 | — |
| Debian:14 | pyjwt | before 2.14.0-1 | 2.14.0-1 |
| openSUSE:Leap 16.0 | python-PyJWT | before 2.12.1-160000.3.1 | 2.12.1-160000.3.1 |
| openSUSE:Tumbleweed | python-PyJWT | before 2.15.1-1.1 | 2.15.1-1.1 |
| PyPI | pyjwt | before 2.14.0 | 2.14.0 |
| SUSE:Linux Enterprise Module for Public Cloud 12 | python-PyJWT | before 1.5.3-3.22.1 | 1.5.3-3.22.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | python-PyJWT | before 2.8.0-150400.8.20.1 | 2.8.0-150400.8.20.1 |
| SUSE:Linux Micro 6.0 | python-PyJWT | before 2.9.0-159998.1.1 | 2.9.0-159998.1.1 |
| SUSE:Linux Micro 6.1 | python-PyJWT | before 2.12.1-slfo.1.1_3.1 | 2.12.1-slfo.1.1_3.1 |
| SUSE:Linux Micro 6.2 | python-PyJWT | before 2.12.1-160000.3.1 | 2.12.1-160000.3.1 |
Same product
pyjwt project: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-102268PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard36Monitor
- CVE-2026-102267PyJWT: PyJWKClient follows redirects when fetching JWKS36Monitor
- CVE-2026-102266PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-102265Sep 28, 2026 · PyJWT: Uncaught RecursionError in jwt.decode() on deeply nested token header21Monitor
- ← EarlierCVE-2026-102269Sep 28, 2026 · PyJWT: Non-canonical signature segments enable raw-token revocation bypass21Monitor
- Later →CVE-2026-102271Sep 28, 2026 · PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| jpadilla pyjwt | 2.14.0 · description | Vendor (CNA) |
| azl3 python-jwt 2.13.0-1 on Azure Linux 3.0 | 2.15.1-1 · Release Notes | Microsoft (MSRC) |
| debian:pyjwt | 2.14.0-1 · Debian:14 | Package registry (OSV) |
| opensuse:python-PyJWT | 2.15.1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:pyjwt | 2.14.0 | Package registry (OSV) |
| suse:python-PyJWT | 2.12.1-160000.3.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+48 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-1333 · Inefficient Regular Expression ComplexityCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- CVSS4.4 → 4.9
- SSVC exploitation— → poc
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.