CVE-2020-26160: jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []stri

Q: How do I fix CVE-2020-26160?

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

Q: Is CVE-2020-26160 being exploited?

CVE-2020-26160 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-2020-26160 affect?

CVE-2020-26160 affects jwt-go. Severity is high (CVSS 7.5). jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []string{} for m["aud"] (which is allowed by the specification). Because the type assertion fails, "" is the value of aud. This is a sec

Q: How urgent is CVE-2020-26160?

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

This month

HIGH 7.5REMOTEUPGRADE

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

jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []string{} for m["aud"] (which is allowed by the specification). Because the type assertion fails, "" is the value of aud. This is a security problem if the JWT token is presented to a service that lacks its own audience check.

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	2.2% (top 18%)
CISA exploited list	No
Weakness	CWE-287, CWE-755
Published	2020-09-30
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jwt-go project

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

Am I affected?

Timeline

2020-09-30 18:15 UTCPublished CVE record published
2026-06-17 03:07 UTCUpdated Record last modified

jwt-go project jwt-go UPGRADE

Affected: <= 3.2.0

Fixed in: newer than 3.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

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

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jwt-go

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-2020-26160?

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

Is CVE-2020-26160 being exploited?

CVE-2020-26160 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-2020-26160 affect?

CVE-2020-26160 affects jwt-go. Severity is high (CVSS 7.5). jwt-go before 4.0.0-preview1 allows attackers to bypass intended access restrictions in situations with []string{} for m["aud"] (which is allowed by the specification). Because the type assertion fails, "" is the value of aud. This is a sec

How urgent is CVE-2020-26160?

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

References

← Back to latest CVEs