CVE-2026-102267

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.4 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-29) is not newer than that change (2026-10-07), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — Patch released this week

Also known asEUVD-2026-88534 (ENISA EUVD) · GHSA-9v7f-9g4p-ffgj (GitHub Security Advisories) · PYSEC-2026-4144 (OSV.dev)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result, PyJWKClient follows the redirect and consumes the redirected response as key material. Consequently, forwarded credentials may be disclosed or verification keys may be substituted. This issue is fixed in version 2.14.0.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
5th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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_release, github, github_commit.
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 0a795b8e1f6e (jpadilla/pyjwt)

Patch available: jpadilla/pyjwt 2.14.0 (contains commit 0a795b8e1f6e)

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

PyJWKClient follows redirects when fetching JWKS · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-9v7f-9g4p-ffgj

Patch Availability(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatfence-agents-0:4.10.0-122.el9_9.12026-11-11redhat
redhatfence-agents-0:4.16.0-34.el10_3.12026-11-11redhat
ubuntupython3-jwt (2.13.0-1ubuntu1) @ stonking2026-11-11ubuntu
ubuntupython3-jwt (1.7.1-2ubuntu2.1+esm3) @ focal2026-11-11ubuntu
redhatrhtas/rh-sigstore-a2a-rhel9:17936241222026-11-04redhat
redhatfence-agents-0:4.16.0-5.el10_0.142026-11-04redhat
redhatfence-agents-0:4.16.0-21.el10_2.72026-11-03redhat
redhatfence-agents-0:4.10.0-110.el9_8.82026-11-03redhat
redhatfence-agents-0:4.10.0-62.el9_4.312026-11-03redhat
redhatfence-agents-0:4.10.0-86.el9_6.232026-11-03redhat
redhatfence-agents-0:4.10.0-43.el9_2.272026-11-03redhat
redhatsatellite/foreman-mcp-server-rhel9:17932722762026-10-29redhat
redhatrhelai3/bootc-rocm-rhel9:17931358632026-10-29redhat
redhatrhoai/odh-kserve-storage-initializer-rhel9:17926850672026-10-29redhat
redhatrhelai3/disk-image-cuda-rhel9:17932067582026-10-29redhat
redhatsatellite/iop-host-inventory-rhel9:17932485832026-10-29redhat
redhatsatellite/iop-host-inventory-rhel9:17932486892026-10-29redhat
redhatsatellite/foreman-mcp-server-rhel9:17932722792026-10-29redhat
redhatpython3.12-pyjwt-0:2.14.0-1.el9ap2026-10-21redhat
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17919448192026-10-21redhat
redhatansible-automation-platform-27/metrics-service-rhel9:17923872162026-10-21redhat
redhatrhtas/model-transparency-rhel9:17924027392026-10-19redhat
redhatrhaii/vllm-cuda-rhel9:17914736312026-10-13redhat
redhatrhaii/vllm-gaudi-rhel9:17914271822026-10-13redhat
redhatrhaii/vllm-rocm-rhel9:17914258692026-10-13redhat
redhatrhaii/vllm-cpu-rhel9:17914736142026-10-13redhat
redhatrhaii/vllm-spyre-rhel9:17918183572026-10-13redhat
pipPyJWT @ 2.14.0 (fixes <= 2.13.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, 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(3)

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

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 21× in last 7d / 76× 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 193 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 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-102267?
CVE-2026-102267 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, PyJWT PyJWKClient is affected because redirect destinations are not revalidated against the JWKS trust boundary. This occurs when a configured trusted JWKS endpoint returns an attacker-influenced redirect. As a result,…
When was the CVE record for CVE-2026-102267 published?
The CVE record for CVE-2026-102267 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-102267 actively exploited?
CVE-2026-102267 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102267?
CVE-2026-102267 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-102267?
A fix for CVE-2026-102267 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102267 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-102267

Explore →

Is Your Infrastructure Affected by CVE-2026-102267?

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