CVE-2015-9235

Exp

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).

Published: 2018-05-29 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2015-9235 is rated High Exploit Risk (93.2/100): CVSS Critical severity, with high exploitation likelihood (EPSS 37.48%, 97th percentile). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +5.01% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2015-9235

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2015-9235

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-23 32.47% 37.48% +5.01%
2 2026-03-23 37.07% 32.47% -4.60%
3 2026-03-21 — 37.07% —

Full EPSS history (22 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2015-9235

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2015-9235

GitHub Security Advisory for CVE-2015-9235

GHSA-c7hr-j4mj-j2w6 · Severity: critical · Ecosystem: npm — Verification Bypass in jsonwebtoken

OS Trackers for CVE-2015-9235

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2015-9235

Affected software / configurations for CVE-2015-9235

Vendor Product Version Raw CPE
auth0 jsonwebtoken < 4.2.2 cpe:2.3:a:auth0:jsonwebtoken:*:*:*:*:*:node.js:*:*

References for CVE-2015-9235

cvelogic Threat Intelligence