CVE-2020-26160

Description

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.

Severity
HIGH
CVSS v3
7.5
CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:N · source cna
Exploit chance (EPSS)
2.158%
chance of exploitation in the next 30 days
higher than 82.5% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
None public
Exploit references (NVD and CNA): 0
Metasploit modules: 0
Nuclei templates: 0

Weakness

Timeline

  1. 2020-09-30Published by the CNA12:57 UTC
  2. 2021-05-18GitHub advisory published (GHSA-w73w-5m7g-f7qc)230 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-w73w-5m7g-f7qc, affected packages:

PackageVulnerable versionsFixed in
Go github.com/dgrijalva/jwt-gofrom 0.0.0-20150717181359-44718f8a89b0 through 3.2.0
Go github.com/dgrijalva/jwt-go/v4before 4.0.0-preview14.0.0-preview1

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
jwt-go_project jwt-gothrough 3.2.0no fix listednot listed

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources