CVE-2026-48526

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-15. A secondary CVSS source baseline 7.4; 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-32917 (ENISA EUVD) · GHSA-xgmm-8j9v-c9wx (GitHub Security Advisories) · PYSEC-2026-179 (OSV.dev)Source: ENISA EUVD

7.4EG
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: 7.4Exploit: 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, 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.4HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
37th
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-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-11-10). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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 May 29, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-feature-server-rhel9:17921485232026-10-21redhat
redhatrhoai/odh-feature-server-rhel9:17918632202026-10-19redhat
redhatrhelai3/bootc-rocm-rhel9:17906144472026-10-05redhat
redhatrhelai3/disk-image-cuda-rhel9:17909574172026-10-05redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-spyre-rhel9:17900761412026-09-23redhat
redhatrhaii/vllm-rocm-rhel9:17901096202026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatrhaii/vllm-spyre-rhel9:17896812012026-09-21redhat
redhatrhaii/vllm-cpu-rhel9:17896811282026-09-21redhat
redhatrhaii/vllm-rocm-rhel9:17896811262026-09-21redhat
redhatrhaii/vllm-cuda-rhel9:17896811262026-09-21redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhoai/odh-latency-predictor-training-rhel9:17865522502026-08-26redhat
redhatrhtas/model-transparency-rhel9:17854204252026-08-05redhat
redhatpython-pyjwt-0:2.13.0-1.el9pc2026-08-04redhat
redhatansible-automation-platform-27/gateway-rhel9:17854359702026-08-04redhat
redhatpython3.12-pyjwt-0:2.13.0-1.el9pc2026-08-04redhat
redhatautomation-controller-0:4.6.31-1.el9ap2026-08-04redhat
redhatautomation-controller-0:4.7.15-2.el9ap2026-08-04redhat
redhatquay/quay-rhel9:17849872732026-07-29redhat
redhatmta/mta-solution-server-rhel9:17841098832026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatrhoai/odh-llama-stack-core-rhel9:17837015982026-07-21redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17840465112026-07-20redhat
redhatansible-automation-platform-tech-preview/metrics-service-rhel9:17839691392026-07-20redhat
redhatansible-automation-platform-27/metrics-service-rhel9:17839205422026-07-20redhat
pippyjwt @ 2.13.0 (fixes < 2.13.0)—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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
pyjwt1.7.1-2 ... 2.7.0-1 (16 versions)
  • every version on: no fix on record
—
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)
  • 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.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× 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 309 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 209 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-48526?
CVE-2026-48526 is a high-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, 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 the CVE record for CVE-2026-48526 published?
The CVE record for CVE-2026-48526 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-48526 actively exploited?
CVE-2026-48526 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48526?
CVE-2026-48526 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-48526?
A fix for CVE-2026-48526 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48526 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-48526

Explore →

Is Your Infrastructure Affected by CVE-2026-48526?

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