CVE-2026-48525

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

Score 5.3 from GitHub Security Advisory (severity: MODERATE) published 2026-06-15. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-32919 (ENISA EUVD) · GHSA-w7vc-732c-9m39 (GitHub Security Advisories) · PYSEC-2026-178 (OSV.dev)Source: ENISA EUVD

5.3EG
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.4%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

PyJWT is a JSON Web Token implementation in Python. From 2.8.0 to 2.12.1, when verifying detached JWS tokens using the unencoded-payload option ("b64": false, RFC 7797), PyJWT performs Base64URL decoding of the compact-serialization payload segment before enforcing the detached-payload rules. For b64=false, PyJWT later discards that decoded payload and replaces it with the caller-provided detached_payload. In practice, this turns the middle segment into an attacker-controlled “work amplifier”: a remote client can supply an arbitrarily large Base64URL payload segment that forces CPU work + memory allocations even if the signature is invalid. This creates an unauthenticated DoS vector against any endpoint that verifies detached JWS using PyJWT. This vulnerability is fixed in 2.13.0.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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 or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 or medium mission impact; Attend at high (mission-essential systems).

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 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)14 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 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 25, 2026

Advisory Details (1)

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

Unauthenticated DoS via unbounded Base64URL decoding of unused payload segment in b64=false detached JWS · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-w7vc-732c-9m39

Vendor Advisories for CVE-2026-48525(2)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-jwt (2.10.1-4ubuntu1.1) @ resolute2026-10-25ubuntu
pippyjwt @ 2.13.0 (fixes >= 2.8.0, <= 2.12.1)—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.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
pyjwt2.10.0 ... 2.9.0 (7 versions)
  • 2.8.0 up to 2.13.0: fixed in 2.13.0
—

Weakness Classification(1)

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 7× in last 7d / 33× 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 221 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 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48525?
CVE-2026-48525 is a medium-severity vulnerability; its CVE record was published on May 28, 2026. PyJWT is a JSON Web Token implementation in Python. From 2.8.0 to 2.12.1, when verifying detached JWS tokens using the unencoded-payload option ("b64": false, RFC 7797), PyJWT performs Base64URL decoding of the compact-serialization payload segment before enforcing the detached-payload rules. For…
When was the CVE record for CVE-2026-48525 published?
The CVE record for CVE-2026-48525 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 25, 2026; the record at its source may have been updated since.
Is CVE-2026-48525 actively exploited?
CVE-2026-48525 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48525?
CVE-2026-48525 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48525?
A fix for CVE-2026-48525 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48525 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-48525

Explore →

Is Your Infrastructure Affected by CVE-2026-48525?

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