CVE-2015-9235

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 37.5%, top 3% 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, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 9%CVSS: 9.8Exploit: NoneExposed: 0

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

In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
94.5%
KEV
Not listed

Published

May 29, 2018

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Jun 6, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

Critical vulnerabilities in JSON Web Token libraries

https://www.timmclean.net/2015/02/25/jwt-alg-none.html
github_commit

commit 1bb584bc3822 (auth0/node-jsonwebtoken)

Fix landed in auth0/node-jsonwebtoken commit 1bb584bc3822 — awaiting tagged release

https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
jsonwebtoken—4.2.2—

Weakness Classification(2)

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

Data Freshness Timeline

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

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCz-bool/Venom-JWT
    First seen Jan 27, 2025

    针对JWT渗透开发的漏洞验证/密钥爆破工具，针对CVE-2015-9235/空白密钥/未验证签名攻击/CVE-2016-10555/CVE-2018-0114/CVE-2020-28042的结果生成用于FUZZ，也可使用字典/字符枚举(包括JJWT)的方式进行爆破(JWT Crack)

    Open source ↗
  • GitHub PoCNxvh1337/CVE-2015-9235_JWT_key_confusion
    First seen Sep 10, 2023

    automate CVE-2015-9235 exploitation

    Open source ↗
  • GitHub PoCaalex954/jwt-key-confusion-poc
    First seen Jan 13, 2022

    JWT Key Confusion PoC (CVE-2015-9235) Written for the Hack the Box challenge - Under Construction

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2015-9235?
CVE-2015-9235 is a critical vulnerability published on May 29, 2018. In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token digitally signed with an asymmetric key (RS/ES family) of algorithms but instead the attacker send a token digitally signed with a symmetric algorithm (HS* family).
When was CVE-2015-9235 disclosed?
CVE-2015-9235 was first published in the National Vulnerability Database on May 29, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-9235 actively exploited?
CVE-2015-9235 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2015-9235?
CVE-2015-9235 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2015-9235?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-9235, 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-2015-9235

Explore →

Is Your Infrastructure Affected by CVE-2015-9235?

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

Start Free Scan →Browse All CVEs