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.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 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)
EPSS
31.9%
KEV
Not listed

Published

May 28, 2026

Last Modified

July 22, 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(17)

Vendor / EcosystemFixed in / PatchReleasedSource
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
redhatpython3.12-pyjwt-0:2.13.0-1.el9pc2026-07-01redhat
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
redhatquay/quay-rhel8:17819373572026-06-25redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat
redhatquay/quay-rhel8:17818780702026-06-23redhat
redhatfence-agents-0:4.10.0-110.el9_8.32026-06-16redhat
redhatansible-automation-platform-27/mcp-tools-rhel9:17810303182026-06-15redhat
redhatfence-agents-0:4.16.0-21.el10_2.22026-06-15redhat

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

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

(5)

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

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 July 22, 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 31.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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