CVE-2017-10862: jwt-scala 1.2.2 and earlier fails to verify token signatures correctly which may lead to an attacker being abl
CVE-2017-10862 is a medium-severity flaw (CVSS 5.3) affecting jwt-scala. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
jwt-scala 1.2.2 and earlier fails to verify token signatures correctly which may lead to an attacker being able to pass specially crafted JWT data as a correctly signed token.
Why this priority
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.6% (top 52%) |
| CISA exploited list | No |
| Weakness | CWE-345 |
| Published | 2017-10-12 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-10862?
jwt-scala: upgrade to newer than 1.2.2. Exact commands for each OS are on this page.
Is CVE-2017-10862 being exploited?
CVE-2017-10862 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-10862 affect?
CVE-2017-10862 affects jwt-scala. Severity is medium (CVSS 5.3). jwt-scala 1.2.2 and earlier fails to verify token signatures correctly which may lead to an attacker being able to pass specially crafted JWT data as a correctly signed token.
How urgent is CVE-2017-10862?
Priority 36/100. Remotely exploitable, no login, no user action