CVE-2026-48522

MEDIUMPre-NVD 4.24.2
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-32915 (ENISA EUVD) · GHSA-993g-76c3-p5m4 (GitHub Security Advisories)Source: ENISA EUVD

4.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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: 4.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient passes its uri argument directly to urllib.request.urlopen() which uses Python stdlib's default OpenerDirector registering HTTPHandler, HTTPSHandler, FTPHandler, FileHandler, and DataHandler. There is currently no documented option to restrict which schemes PyJWKClient will fetch. If an application's jku URL ingestion path accepts attacker-influenced URLs (e.g., from JWT header, configuration file, OAuth flow parameter), the attacker can cause PyJWKClient to read arbitrary local files via file:// (SSRF on local filesystem), cause PyJWKClient to attempt FTP / data-URI fetches (broader SSRF surface), or forge tokens that PyJWT verifies as valid. The library does not directly return non-HTTP(S) URI contents to the attacker; the chained "plant a JWKS to forge tokens" scenario described in the original report requires additional application-layer flaws (attacker write access to a filesystem path, untrusted jku derivation) that this fix does not address. This vulnerability is fixed in 2.13.0.

CVSS v3
4.2
EG Score
4.2MEDIUMmedium confidence
EG Risk
35
EG Risk 35/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)
Severity42% × 45%
Impact severity (EG Severity): CVSS 4.2 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.
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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
12th
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 (4.2): severity, escalated by confirmed exploitation. This CVE's 4.2 is its impact severity (EG Severity), not escalated.

EG Severity
4.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: 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 public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

May 28, 2026

Last Modified

October 26, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

PyJWKClient: missing scheme allowlist enables CVE-2024-21643-class SSRF + token forgery via file://, ftp://, data: schemes · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-993g-76c3-p5m4

Vendor Advisories for CVE-2026-48522(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-jwt (1.7.1-2ubuntu2.1+esm2) @ focal2026-10-22ubuntu

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.10.1-3, 2.10.1-4, 2.11.0-2, 2.12.1-1
  • every version up to 2.13.0-1: fixed in 2.13.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt0.1.1 ... 2.9.0 (54 versions)
  • 2.0.0 up to 2.13.0: fixed in 2.13.0
  • every version up to 2.13.0: fixed in 2.13.0
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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 9× in last 7d / 39× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 202 refreshes 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 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48522?
CVE-2026-48522 is a medium-severity vulnerability; its CVE record was published on May 28, 2026. PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient passes its uri argument directly to urllib.request.urlopen() which uses Python stdlib's default OpenerDirector registering HTTPHandler, HTTPSHandler, FTPHandler, FileHandler, and DataHandler. There is currently no…
When was the CVE record for CVE-2026-48522 published?
The CVE record for CVE-2026-48522 was published on May 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-48522 actively exploited?
CVE-2026-48522 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48522?
CVE-2026-48522 has a CVSS base score of 4.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48522?
A fix for CVE-2026-48522 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48522 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-48522

Explore →

Is Your Infrastructure Affected by CVE-2026-48522?

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

Book a Demo →Browse All CVEs