Skip to main content
Public proof of conceptFix available

CVE-2015-9235

A public proof of concept exists; no exploitation attested.

  • Published2018-05-29
  • Fixed in4.2.2
  • WeaknessCWE-20 · CWE-327

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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

Timeline

dates in UTC
  1. 2018-05-2920:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-02 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2015-9235?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2015-9235?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Auth0 jsonwebtoken
BranchAffectedFixed in
4.2< 4.2.24.2.2

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.1.0-root.io.1
  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.1.0-root.io.2
  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.1.0-root.io.3
  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.1.0-root.io.4
  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.1.0-root.io.5
  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.4.0-root.io.1
  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.4.0-root.io.2
  • @rootio/jsonwebtokenRoot:npmall versions · fixed in 0.4.0-root.io.3

11 more package ranges on OSV.dev

Vendor advisories

  • CVE-2015-9235 Red Hat Product Security

    nodejs-jsonwebtoken: verification step bypass with an altered token

Full record on NVD

Fix

  1. Update Auth0 jsonwebtoken to 4.2.2

Advisories and patches

Detection

read 2026-11-01 22:42 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
4 repositories, unverifiedaalex954/jwt-key-confusion-pocNxvh1337/CVE-2015-9235_JWT_key_confusionz-bool/Venom-JWTtierChampion/POC_CVE-2015-9235
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVSS 3.09.8read 2026-10-23
  • NVDCVSS 2.07.5read 2026-10-23
  • CNAweakness (CWE)CWE-20known since 2026-10-23
  • NVDweakness (CWE)CWE-327read 2026-10-23
  • FIRST EPSSEPSS score8.5 %2026-11-02
  • PoC-in-GitHubproof of concept4read 2026-11-01
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryCRITICAL2020-06-16

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2018-05-29
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-c7hr-j4mj-j2w6

Frequently asked questions

What is CVE-2015-9235?

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

Is CVE-2015-9235 actively exploited?

Active exploitation of CVE-2015-9235 has not been confirmed. Its EPSS score was 8.5% on 2026-11-02, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2015-9235?

CVE-2015-9235 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running jsonwebtoken? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record