CVE-2026-48526

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.4%, top 68% 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: epss, secondary
Elevated
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%CVSS: 7.4Exploit: Elevated riskExposed: 0

A fix is available — apply it.

PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate use of JSON Web Keys in HMAC algorithm, allowing attacker to use the issuer public key as the secret key for HMAC algorithm. This vulnerability is fixed in 2.13.0.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
49(Track*)
EG Risk 49/100SSVC: Track*

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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

May 28, 2026

Last Modified

August 28, 2026

Advisory Details (1)

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

Public-key JWK accepted as HMAC secret enables forged HS256 tokens when mixed families are allowed · Advisory · jpadilla/pyjwt · GitHub

https://github.com/jpadilla/pyjwt/security/advisories/GHSA-xgmm-8j9v-c9wx

Vendor Advisories for CVE-2026-48526(20)

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

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhtas/model-transparency-rhel9:17854204252026-08-05redhat
redhatpython3.12-pyjwt-0:2.13.0-1.el9pc2026-08-04redhat
redhatpython-pyjwt-0:2.13.0-1.el9pc2026-08-04redhat
redhatautomation-controller-0:4.6.31-1.el9ap2026-08-04redhat
redhatansible-automation-platform-27/gateway-rhel9:17854359702026-08-04redhat
redhatautomation-controller-0:4.7.15-2.el9ap2026-08-04redhat
redhatquay/quay-rhel9:17849872732026-07-29redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat
redhatrhoai/odh-llama-stack-core-rhel9:17837015982026-07-21redhat
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17839691392026-07-20redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17840465112026-07-20redhat
redhatansible-automation-platform-27/metrics-service-rhel9:17839205422026-07-20redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatrhtas/segment-reporting-rhel9:17840165542026-07-16redhat
redhatrhoai/odh-kserve-storage-initializer-rhel9:17830102252026-07-09redhat
redhatsatellite/foreman-mcp-server-rhel9:17827393442026-07-07redhat
redhatfence-agents-0:4.10.0-62.el9_4.262026-07-06redhat
redhatfence-agents-0:4.10.0-86.el9_6.182026-07-06redhat
redhatfence-agents-0:4.16.0-5.el10_0.112026-07-06redhat
redhatfence-agents-0:4.10.0-43.el9_2.232026-07-06redhat
redhatansible-automation-platform-26/mcp-tools-rhel9:17827120062026-07-01redhat
redhatpython3.12-pyjwt-0:2.13.0-1.el9ap2026-07-01redhat
redhatquay/quay-rhel8:17824877172026-06-30redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat
redhatquay/quay-rhel8:17819373572026-06-25redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pyjwt1.7.1-2 ... 2.7.0-1 (16 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pyjwt2.10.1-1 ... 2.7.0-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pyjwt2.10.1-2 ... 2.13.0-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pyjwt2.10.1-2, 2.10.1-3, 2.10.1-4, 2.11.0-2, 2.12.1-12.13.0-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pyjwt0.1.1 ... 2.9.0 (54 versions)2.13.0—

Weakness Classification(2)

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

Additional Vendor Advisories

(15)

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 6× in last 7d / 74× 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.

Showing the most recent 100 of 222 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48526?
CVE-2026-48526 is a high vulnerability published on May 28, 2026. PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens, while supporting both asymmetric and HMAC algorithms, the library does not validate use of JSON Web Keys in HMAC algorithm, allowing attacker to use the issuer public key as the…
When was CVE-2026-48526 disclosed?
CVE-2026-48526 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48526 actively exploited?
CVE-2026-48526 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.2% of all scored CVEs.
What is the CVSS score of CVE-2026-48526?
CVE-2026-48526 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-48526?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48526, 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-48526

Explore →

Is Your Infrastructure Affected by CVE-2026-48526?

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

Start Free Scan →Browse All CVEs