Skip to content

← Actionable
High, CVSS 7.5

Authorization bypass in github.com/dgrijalva/jwt-go

CVE-2020-26160GHSA-w73w-5m7g-f7qc

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go github.com/dgrijalva/jwt-go/v4

    Affected
    < 4.0.0-preview1
    Fixed in
    4.0.0-preview1
  • Go github.com/dgrijalva/jwt-go

    Affected
    >= 0.0.0-20150717181359-44718f8a89b0, <= 3.2.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2020-26160: 2.16% estimated exploitation activity in the next 30 days; percentile 82.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 at version 3.2.1

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-w73w-5m7g-f7qc

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-26160

Advisory: Authorization bypass in github.com/dgrijalva/jwt-go
IDs: CVE-2020-26160, GHSA-w73w-5m7g-f7qc
Record: https://patchnext.com/advisories/cve-2020-26160 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/dgrijalva/jwt-go/v4 4.0.0-preview1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dgrijalva/jwt-go/v4: affected < 4.0.0-preview1; fixed in 4.0.0-preview1
- Go github.com/dgrijalva/jwt-go: affected >= 0.0.0-20150717181359-44718f8a89b0, <= 3.2.0

## Suggested inspection (read-only)
- Go github.com/dgrijalva/jwt-go/v4: check the installed version with your package manager.
- Go github.com/dgrijalva/jwt-go: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dgrijalva/jwt-go/v4, github.com/dgrijalva/jwt-go.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w73w-5m7g-f7qc (GitHub-reviewed advisory GHSA-w73w-5m7g-f7qc lists affected ranges: Go github.com/dgrijalva/jwt-go/v4 >=0 =0.0.0-20150717181359-44718f8a89b0 <=3.2.0)

Commands are suggestions: review each one before running it.

Loading voting…