{"id":"CVE-2017-10862","url":"https://www.cyber-defence.io/tools/cve/CVE-2017-10862","generatedAt":"2026-10-28T20:08:41.936Z","title":"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.","description":"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.","published":"2017-10-12T14:29:00.000Z","lastModified":"2026-06-17T01:00:50.000Z","status":"Modified","sourceIdentifier":"vultures@jpcert.or.jp","cvss":{"version":"3.0","score":5.3,"severity":"MEDIUM","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"},"cwe":["CWE-345"],"affected":["really/jwt-scala"],"epss":{"score":0.00583,"percentile":0.47693,"date":"2026-10-27","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.58%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"https://github.com/reallylabs/jwt-scala","tags":["Third Party Advisory"],"source":"vultures@jpcert.or.jp"},{"url":"https://jvn.jp/en/vu/JVNVU90916766/index.html","tags":["Third Party Advisory","VDB Entry"],"source":"vultures@jpcert.or.jp"},{"url":"https://github.com/reallylabs/jwt-scala","tags":["Third Party Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"https://jvn.jp/en/vu/JVNVU90916766/index.html","tags":["Third Party Advisory","VDB Entry"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2017-10862","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}