CVE-2020-26160

unknown

Published 2021-05-18 · Modified 2026-03-13

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS v4 NEW

—

not yet in upstream

VIR risk

—

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.

Predictions

Exploit likelihood

30%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

Debian Fixed 2 releases

Version	Status	Fixed in
bullseye	Fixed	`3.2.0-3`
bookworm	Fixed	`3.2.0-3`

Package impact

Ecosystem	Package	Vulnerable	Fixed
Go	github.com/dgrijalva/jwt-go	`>=0.0.0-20150717181359-44718f8a89b0,<=3.2.0`
Go	github.com/dgrijalva/jwt-go/v4	`<4.0.0-preview1`	`4.0.0-preview1`
Go	github.com/dgrijalva/jwt-go	`>=0.0.0-20150717181359-44718f8a89b0`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.