Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

n/a · Vulnerability

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS 2.0 · [email protected] · Primary 5.0 MEDIUMCVSS_V3 Publisher rating HIGHFixed by github.com/dgrijalva/jwt-go/v4 4.0.0-preview1osv · severity unknownFixed by github.com/dgrijalva/jwt-go/v4 4.0.0-preview1KEV status unknown

cve-program · CVE-2020-26160

Published

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.

Read the publisher's advisory

euvd · EUVD-2021-1212

Published

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.

Read the publisher's advisory

nvd · CVE-2020-26160

Published

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.

Read the publisher's advisory

osv · GHSA-w73w-5m7g-f7qc

Published

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

Read the publisher's advisory

osv · GO-2020-0017

Published

If a JWT contains an audience claim with an array of strings, rather than a single string, and MapClaims.VerifyAudience is called with req set to false, then audience verification will be bypassed, allowing an invalid set of audiences to be provided.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2020-26160

Published

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…

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.

Source published
30 Sep 2020 12:57:10 UTC
Source modified
4 Aug 2024 15:49:07 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

euvd · EUVD-2021-1212

Published

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…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 30, 2020, 12:57:10 PM

dateUpdated: Aug 4, 2024, 3:49:07 PM

10 related source bulletins · separate from aliases

RHSA-2021:0516: Red Hat Security Advisory: Release of OpenShift Serverless 1.13.0 security update

CVE-2020-26160

RHSA-2021:5110: Red Hat Security Advisory: Cryostat security update

CVE-2020-26160

msrc_CVE-2020-26160: 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.

CVE-2020-26160

RHSA-2021:2438: Red Hat Security Advisory: OpenShift Container Platform 4.8.2 bug fix and security update

CVE-2016-2183 · CVE-2020-7774 · CVE-2020-15106 · CVE-2020-15112 · CVE-2020-15113 · CVE-2020-15114 · CVE-2020-15136 · CVE-2020-26160 · CVE-2020-28469 · CVE-2020-28500 · CVE-2020-28852 · CVE-2021-3114 · CVE-2021-3121 · CVE-2021-20206 · CVE-2021-20218 · CVE-2021-20291 · CVE-2021-22133 · CVE-2021-23337 · CVE-2021-23362 · CVE-2021-23368 · CVE-2021-23382 · CVE-2021-26539 · CVE-2021-26540 · CVE-2021-27292 · CVE-2021-28092 · CVE-2021-29059 · CVE-2021-29622 · CVE-2021-33194

RHSA-2021:2042: Red Hat Security Advisory: Red Hat OpenShift Container Storage 4.7 RPM security, bug fix, and enhancement update

CVE-2020-26160 · CVE-2020-28362

RHSA-2021:0799: Red Hat Security Advisory: OpenShift Virtualization 2.6.0 security and bug fix update

CVE-2020-9283 · CVE-2020-14040 · CVE-2020-15586 · CVE-2020-16845 · CVE-2020-26160 · CVE-2020-27813 · CVE-2020-28362 · CVE-2020-29652 · CVE-2021-3121 · CVE-2021-20206

openSUSE-SU-2024:11668-1: velero-plugin-for-microsoft-azure-1.3.1-1.1 on GA media

CVE-2020-26160

openSUSE-SU-2024:11428-1: telegraf-1.19.0-1.2 on GA media

CVE-2020-26160

RHSA-2020:5633: Red Hat Security Advisory: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update

CVE-2020-7774 · CVE-2020-8563 · CVE-2020-10749 · CVE-2020-10763 · CVE-2020-14040 · CVE-2020-26160 · CVE-2020-27813 · CVE-2020-27846 · CVE-2020-28362 · CVE-2020-29652 · CVE-2021-3121 · CVE-2021-26539

RHSA-2021:2041: Red Hat Security Advisory: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement update

CVE-2020-7608 · CVE-2020-7774 · CVE-2020-8565 · CVE-2020-26160 · CVE-2020-26289 · CVE-2020-28362 · CVE-2021-3114 · CVE-2021-3528

Source published
Sep 30, 2020, 12:57:10 PM (timezone not stated)
Source modified
Aug 4, 2024, 3:49:07 PM (timezone not stated)
Saved here
17 Nov 2026 23:32:50 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

nvd · CVE-2020-26160

Published

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…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-287 · CWE-755

Original publisher date fields

published: 2020-09-30T18:15:27.397

lastModified: 2026-06-17T03:07:43.907

1 source CPE criteria · context only
  • cpe:2.3:a:jwt-go_project:jwt-go:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
30 Sep 2020 18:15:27 UTC
Source modified
17 Jun 2026 03:07:43 UTC
Saved here
24 Oct 2026 16:17:32 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS 3.1 · [email protected] · Primary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS 2.0 · [email protected] · Primary · 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

osv · GHSA-w73w-5m7g-f7qc

Published

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

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

Source published
18 May 2021 21:08:21 UTC
Source modified
10 Sep 2026 03:49:05 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

Publisher rating · HIGH

osv · GO-2020-0017

Published

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

If a JWT contains an audience claim with an array of strings, rather than a single string, and MapClaims.VerifyAudience is called with req set to false, then audience verification will be bypassed, allowing an invalid set of audiences to be provided.

Source published
14 Apr 2021 20:04:52 UTC
Source modified
8 Jul 2026 06:49:40 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current