CVE-2026-48525

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. 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: cna:github_m, epss
Elevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.3(medium)
EPSS
20.7%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 14, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

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(1)

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
pyjwt2.10.0 ... 2.9.0 (7 versions)2.13.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 49× 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-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 19:53 UTCEG score recompute
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 18:10 UTCEG score recompute
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-07 13:46 UTCEPSS rescore
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-02 14:10 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 02:57 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-29 21:56 UTCEG score recompute
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 20:53 UTCEG score recompute
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
Show 70 more
  1. 2026-06-27 19:50 UTCEG score recompute
  2. 2026-06-27 03:08 UTCEPSS rescore
  3. 2026-06-26 18:47 UTCEG score recompute
  4. 2026-06-25 17:44 UTCEG score recompute
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 16:41 UTCEG score recompute
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-19 19:26 UTCEPSS rescore
  17. 2026-06-19 19:26 UTCEPSS rescore
  18. 2026-06-19 00:40 UTCEG score recompute
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-17 18:12 UTCEG score recompute
  22. 2026-06-17 17:53 UTCEPSS rescore
  23. 2026-06-16 17:53 UTCEPSS rescore
  24. 2026-06-16 17:10 UTCEG score recompute
  25. 2026-06-15 17:49 UTCEPSS rescore
  26. 2026-06-15 17:49 UTCEPSS rescore
  27. 2026-06-15 16:06 UTCEG score recompute
  28. 2026-06-14 23:18 UTCEPSS rescore
  29. 2026-06-14 15:00 UTCEG score recompute
  30. 2026-06-13 23:00 UTCEPSS rescore
  31. 2026-06-13 13:56 UTCEG score recompute
  32. 2026-06-12 23:12 UTCEPSS rescore
  33. 2026-06-12 23:12 UTCEPSS rescore
  34. 2026-06-12 12:40 UTCEG score recompute
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-11 11:37 UTCEG score recompute
  37. 2026-06-10 22:18 UTCEPSS rescore
  38. 2026-06-10 13:22 UTCEPSS rescore
  39. 2026-06-10 13:22 UTCEPSS rescore
  40. 2026-06-10 10:33 UTCEG score recompute
  41. 2026-06-09 09:31 UTCEG score recompute
  42. 2026-06-08 14:17 UTCEPSS rescore
  43. 2026-06-08 14:17 UTCEPSS rescore
  44. 2026-06-08 08:27 UTCEG score recompute
  45. 2026-06-07 15:25 UTCEPSS rescore
  46. 2026-06-07 15:25 UTCEPSS rescore
  47. 2026-06-07 07:24 UTCEG score recompute
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 13:47 UTCEPSS rescore
  50. 2026-06-06 06:21 UTCEG score recompute
  51. 2026-06-05 22:47 UTCEPSS rescore
  52. 2026-06-05 06:10 UTCEPSS rescore
  53. 2026-06-05 06:10 UTCEPSS rescore
  54. 2026-06-05 05:18 UTCEG score recompute
  55. 2026-06-04 13:12 UTCEPSS rescore
  56. 2026-06-04 13:12 UTCEPSS rescore
  57. 2026-06-04 04:15 UTCEG score recompute
  58. 2026-06-03 03:12 UTCEG score recompute
  59. 2026-06-02 20:13 UTCEPSS rescore
  60. 2026-06-02 02:09 UTCEG score recompute
  61. 2026-06-01 13:52 UTCEPSS rescore
  62. 2026-06-01 13:52 UTCEPSS rescore
  63. 2026-06-01 01:06 UTCEG score recompute
  64. 2026-05-31 22:30 UTCEPSS rescore
  65. 2026-05-31 22:30 UTCEPSS rescore
  66. 2026-05-31 00:16 UTCEPSS rescore
  67. 2026-05-31 00:16 UTCEPSS rescore
  68. 2026-05-29 13:44 UTCEPSS rescore
  69. 2026-05-29 13:44 UTCEPSS rescore
  70. 2026-05-28 15:26 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48525?
CVE-2026-48525 is a medium vulnerability 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 CVE-2026-48525 disclosed?
CVE-2026-48525 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48525 actively exploited?
CVE-2026-48525 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48525?
CVE-2026-48525 has a CVSS v4.0 base score of 5.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-48525?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48525, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.