Skip to content
CVE Tracker
Back

CVE-2016-10555

Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent…

Medium6.5EPSS 4.8%
Published
Updated
Reserved
Assigned by
hackerone

Description

Since "algorithm" isn't enforced in jwt.decode()in jwt-simple 0.3.0 and earlier, a malicious user could choose what algorithm is sent sent to the server. If the server is expecting RSA but is sent HMAC-SHA with RSA's public key, the server will think the public key is actually an HMAC private key. This could be used to forge any data an attacker wants.

Scores

CVSS scores of CVE-2016-10555, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.0Medium6.5CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS (exploitation in 30 days)
4.8% · top 8.0% of all CVEs (3 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.5.

Weakness

Affected products

Affected packages

From reviewed advisories of the GitHub Advisory Database.

References (4)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2016-10555 badge
[![CVE-2016-10555](https://trackcve.app/badge/CVE-2016-10555.svg)](https://trackcve.app/cve/CVE-2016-10555)

Record last updated .