CVE-2026-102267

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.4Exploit: 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
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

October 1, 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 Patch Available

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

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

Vendor Advisories for CVE-2026-102267(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pyjwt0.1.1 ... 2.9.0 (55 versions)2.14.0—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 04:49 UTCVendor advisory
  2. 2026-10-03 16:33 UTCEG score recompute
  3. 2026-10-03 16:33 UTCVendor advisory
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 04:16 UTCEG score recompute
  6. 2026-10-03 04:16 UTCVendor advisory
  7. 2026-10-02 15:59 UTCVendor advisory
  8. 2026-10-02 03:40 UTCEG score recompute
  9. 2026-10-02 03:40 UTCVendor advisory
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 15:23 UTCEG score recompute
  12. 2026-10-01 15:23 UTCVendor advisory
  13. 2026-10-01 15:01 UTCEG score recompute
  14. 2026-10-01 15:01 UTCVendor advisory
  15. 2026-10-01 08:01 UTCVendor advisory
  16. 2026-09-30 19:44 UTCEG score recompute
  17. 2026-09-30 19:44 UTCVendor advisory
  18. 2026-09-30 15:02 UTCEPSS rescore
  19. 2026-09-30 12:02 UTCVendor advisory
  20. 2026-09-29 23:45 UTCEG score recompute
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-29 09:39 UTCEG score recompute
  23. 2026-09-28 21:18 UTCEG score recompute
  24. 2026-09-28 20:36 UTCEG score recompute
  25. 2026-09-28 20:36 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-102267?
CVE-2026-102267 is a high vulnerability 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 CVE-2026-102267 disclosed?
CVE-2026-102267 was first published on September 28, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102267?
CVE-2026-102267 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
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.

Book a Demo →Browse All CVEs