CVE-2026-102268

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-29. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-88535 (ENISA EUVD) · GHSA-ffc3-869f-jxw9 (GitHub Security Advisories) · PYSEC-2026-4145 (OSV.dev)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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 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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 28, 2026

Last Modified

October 7, 2026

Advisory Details (3)

Auto-updated Sep 28, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub release Patch Available

2.14.0

Patch available: jpadilla/pyjwt 2.14.0

https://github.com/jpadilla/pyjwt/releases/tag/2.14.0
GitHub commit Patch Available

commit 8b4e233a2220 (jpadilla/pyjwt)

Patch available: jpadilla/pyjwt 2.14.0 (contains commit 8b4e233a2220)

https://github.com/jpadilla/pyjwt/commit/8b4e233a22206b34ec1186e912e75c0b2396ac07
GitHub advisoryMentions a patch (unverified)

Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard, permitting HS256 token forgery under a mixed algorithm allow-list. · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-ffc3-869f-jxw9

Patch Availability(29)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-jwt (1.7.1-2ubuntu2.1+esm3) @ focal2026-11-22ubuntu
ubuntupython3-jwt (2.13.0-1ubuntu1) @ stonking2026-11-22ubuntu
redhatansible-automation-platform-24/ee-supported-rhel9:17943569952026-11-20redhat
redhatansible-automation-platform-24/ee-supported-rhel8:17943125912026-11-20redhat
redhatansible-automation-platform-25/ee-supported-rhel9:17944419022026-11-20redhat
oraclepatch2026-11-17oracle
redhatpython3.12-pyjwt-0:2.15.1-1.el9pc2026-11-13redhat
redhatpython-pyjwt-0:2.15.1-1.el9pc2026-11-12redhat
redhatfence-agents-0:4.10.0-122.el9_9.12026-11-11redhat
redhatfence-agents-0:4.16.0-34.el10_3.12026-11-11redhat
redhatrhtas/model-transparency-rhel9:17942210442026-11-11redhat
redhatquay/quay-rhel9:17939938902026-11-11redhat
redhatquay/quay-rhel8:17939937302026-11-11redhat
redhatquay/quay-rhel9:17939937992026-11-11redhat
redhatquay/quay-rhel8:17939937712026-11-11redhat
redhatquay/quay-rhel8:17939938482026-11-11redhat
redhatquay/quay-rhel8:17939936742026-11-11redhat
redhatquay/quay-rhel9:17939937782026-11-11redhat
redhatquay/quay-rhel8:17939938542026-11-11redhat
redhatfence-agents-0:4.16.0-5.el10_0.142026-11-04redhat
redhatrhtas/model-transparency-rhel9:17936965782026-11-04redhat
redhatrhtas/rh-sigstore-a2a-rhel9:17936241222026-11-04redhat
redhatfence-agents-0:4.10.0-110.el9_8.82026-11-03redhat
redhatfence-agents-0:4.16.0-21.el10_2.72026-11-03redhat
redhatfence-agents-0:4.10.0-86.el9_6.232026-11-03redhat
redhatfence-agents-0:4.10.0-62.el9_4.312026-11-03redhat
redhatfence-agents-0:4.10.0-43.el9_2.272026-11-03redhat
redhatrhelai3/disk-image-cuda-rhel9:17932067582026-10-29redhat
pipPyJWT @ 2.14.0 (fixes <= 2.13.0)—ghsa

These rows come from Ubuntu, Red Hat, Oracle and GitHub (GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-1 ... 2.7.0-1 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-2 ... 2.15.1-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt2.10.1-2 ... 2.13.0-1 (6 versions)
  • every version up to 2.14.0-1: fixed in 2.14.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt0.1.1 ... 2.9.0 (55 versions)
  • every version up to 2.14.0: fixed in 2.14.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(21)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 86× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 250 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 06:39 UTCVendor advisory
  2. 2026-11-22 04:46 UTCEchelonGraph re-scored
  3. 2026-11-22 04:46 UTCVendor advisory
  4. 2026-11-22 04:46 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-11-21 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-11-21 05:37 UTCEchelonGraph re-scored
  7. 2026-11-21 05:37 UTCVendor advisory
  8. 2026-11-21 05:37 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-11-20 06:38 UTCEchelonGraph re-scored
  11. 2026-11-20 06:38 UTCVendor advisory
  12. 2026-11-20 06:38 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-11-19 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-11-19 07:39 UTCEchelonGraph re-scored
  15. 2026-11-19 07:39 UTCVendor advisory
  16. 2026-11-19 07:39 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  18. 2026-11-18 08:40 UTCEchelonGraph re-scored
  19. 2026-11-18 08:40 UTCVendor advisory
  20. 2026-11-18 08:40 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-11-17 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-11-17 09:41 UTCEchelonGraph re-scored
  23. 2026-11-17 09:41 UTCVendor advisory
  24. 2026-11-17 09:41 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-11-16 16:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
Show 75 more
  1. 2026-11-16 10:42 UTCEchelonGraph re-scored
  2. 2026-11-16 10:42 UTCVendor advisory
  3. 2026-11-16 10:42 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-15 16:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  5. 2026-11-15 11:24 UTCEchelonGraph re-scored
  6. 2026-11-15 11:24 UTCVendor advisory
  7. 2026-11-15 11:24 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-14 16:38 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-11-14 12:25 UTCEchelonGraph re-scored
  10. 2026-11-14 12:25 UTCVendor advisory
  11. 2026-11-14 12:25 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-11-13 13:23 UTCEchelonGraph re-scored
  14. 2026-11-13 13:23 UTCVendor advisory
  15. 2026-11-13 13:23 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-11-12 14:18 UTCEchelonGraph re-scored
  18. 2026-11-12 14:18 UTCVendor advisory
  19. 2026-11-12 14:17 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-11-11 15:18 UTCEchelonGraph re-scored
  22. 2026-11-11 15:18 UTCVendor advisory
  23. 2026-11-11 15:18 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-11-10 16:20 UTCVendor advisory
  26. 2026-11-10 16:20 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-11-09 17:17 UTCEchelonGraph re-scored
  28. 2026-11-09 17:17 UTCVendor advisory
  29. 2026-11-09 17:17 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-11-08 18:19 UTCEchelonGraph re-scored
  32. 2026-11-08 18:19 UTCVendor advisory
  33. 2026-11-08 18:19 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  34. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-11-07 19:20 UTCEchelonGraph re-scored
  36. 2026-11-07 19:20 UTCVendor advisory
  37. 2026-11-07 19:20 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  38. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-11-06 20:18 UTCEchelonGraph re-scored
  40. 2026-11-06 20:18 UTCVendor advisory
  41. 2026-11-06 20:18 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  42. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-11-05 21:25 UTCOSV refresh
  44. 2026-11-05 21:19 UTCEchelonGraph re-scored
  45. 2026-11-05 21:19 UTCVendor advisory
  46. 2026-11-05 21:19 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  47. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  48. 2026-11-04 22:20 UTCEchelonGraph re-scored
  49. 2026-11-04 22:20 UTCVendor advisory
  50. 2026-11-04 22:20 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  51. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  52. 2026-11-03 23:12 UTCEchelonGraph re-scored
  53. 2026-11-03 23:12 UTCVendor advisory
  54. 2026-11-03 23:12 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  55. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  56. 2026-11-03 00:13 UTCEchelonGraph re-scored
  57. 2026-11-03 00:13 UTCVendor advisory
  58. 2026-11-03 00:13 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  59. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  60. 2026-11-02 01:12 UTCEchelonGraph re-scored
  61. 2026-11-02 01:12 UTCVendor advisory
  62. 2026-11-02 01:12 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  63. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-ffc3-869f-jxw9 · GitHub severity CRITICAL · GitHub CVSS 9.1
  65. 2026-11-01 08:00 UTCEchelonGraph re-scored
  66. 2026-11-01 02:11 UTCEchelonGraph re-scored
  67. 2026-11-01 02:11 UTCVendor advisory
  68. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  69. 2026-10-31 03:12 UTCEchelonGraph re-scored
  70. 2026-10-31 03:12 UTCVendor advisory
  71. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  72. 2026-10-30 04:12 UTCEchelonGraph re-scored
  73. 2026-10-30 04:12 UTCVendor advisory
  74. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  75. 2026-10-29 05:12 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-102268?
CVE-2026-102268 is a critical-severity vulnerability; its CVE record was published on September 28, 2026. 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 algorithms and…
When was the CVE record for CVE-2026-102268 published?
The CVE record for CVE-2026-102268 was published on September 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-102268 actively exploited?
CVE-2026-102268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102268?
CVE-2026-102268 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102268?
A fix for CVE-2026-102268 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102268 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-102268

Explore →

Is Your Infrastructure Affected by CVE-2026-102268?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.