Answer in brief
CVE-2020-26160 records a High severity (CVSS 7.5) vulnerability in Authorization bypass in github.com/dgrijalva/jwt-go. The current sources do not mark it as known exploited. The current feed maps github.com/dgrijalva/jwt-go (go), github.com/dgrijalva/jwt-go/v4 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps github.com/dgrijalva/jwt-go (go), github.com/dgrijalva/jwt-go/v4 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| github.com/dgrijalva/jwt-gogo | >=0.0.0-20150717181359-44718f8a89b0 | Not reported |
| github.com/dgrijalva/jwt-go/v4go | >=0 <4.0.0-preview1 | 4.0.0-preview1 |
Published upstream
Apr 14, 2021
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
jwt-go 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. There is no patch available and users of jwt-go are advised to migrate to [golang-jwt](https://github.com/golang-jwt/jwt) at version 3.2.1
Quoted source text, attributed separately from HOL analysis.