CVE-2018-1000531: inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnera

Q: How do I fix CVE-2018-1000531?

prime-jwt: upgrade to newer than 1.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2018-1000531 being exploited?

CVE-2018-1000531 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-1000531 affect?

CVE-2018-1000531 affects prime-jwt. Severity is high (CVSS 7.5). inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnerability in JWTDecoder.decode that can result in an incorrect signature validation of a JWT token. This attack can be exploitable wh

Q: How urgent is CVE-2018-1000531?

Priority 50/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2018-1000531 is a high-severity flaw (CVSS 7.5) affecting prime-jwt. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnerability in JWTDecoder.decode that can result in an incorrect signature validation of a JWT token. This attack can be exploitable when an attacker crafts a JWT token with a valid header using 'none' as algorithm and a body to requests it be validated. This vulnerability was fixed after commit abb0d479389a2509f939452a6767dc424bb5e6ba.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 23%)
CISA exploited list	No
Weakness	CWE-20
Published	2018-06-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: inversoft

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-26 16:29 UTCPublished CVE record published
2026-06-17 01:32 UTCUpdated Record last modified

inversoft prime-jwt UPGRADE

Affected: <= 1.3.0

Fixed in: newer than 1.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy prime-jwt || rpm -q prime-jwt || prime-jwt --version

2. UPGRADE to newer than 1.3.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade prime-jwt

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade prime-jwt

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
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-2018-1000531?

prime-jwt: upgrade to newer than 1.3.0. Exact commands for each OS are on this page.

Is CVE-2018-1000531 being exploited?

CVE-2018-1000531 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-2018-1000531 affect?

CVE-2018-1000531 affects prime-jwt. Severity is high (CVSS 7.5). inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnerability in JWTDecoder.decode that can result in an incorrect signature validation of a JWT token. This attack can be exploitable wh

How urgent is CVE-2018-1000531?

Priority 50/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2018-1000125 CRITICAL 9.8 UPGRADE inversoft prime-jwt version prior to version 1.3.0 or prior to commit 0d94dcef0133d699f21d217e922564adbb83a227

References

← Back to latest CVEs