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
This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 2.2% (81st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 39EG Risk 39/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation2% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 2.2%
- EPSS %ILE
- 81st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 30, 2020
Last Modified
November 21, 2024
References (4)
- cve@mitrehttps://github.com/dgrijalva/jwt-go/pull/426
- cve@mitrehttps://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
- af854a3a-2127-422b-91ae-364da2661108https://github.com/dgrijalva/jwt-go/pull/426
- af854a3a-2127-422b-91ae-364da2661108https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMDGRIJALVAJWTGO-596515
Vendor Advisories for CVE-2020-26160(7)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2020-26160Microsoft Security Response Center (MSRC)
CVE-2020-26160
- RHSA-2021:5110Red Hat Product SecurityMedium
Red Hat Security Advisory: Cryostat security update
- RHSA-2021:2438Red Hat Product SecurityMedium
Red Hat Security Advisory: OpenShift Container Platform 4.8.2 bug fix and security update
- RHSA-2021:2042Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat OpenShift Container Storage 4.7 RPM security, bug fix, and enhancement update
- RHSA-2021:2041Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement update
- RHSA-2021:0799Red Hat Product SecurityMedium
Red Hat Security Advisory: OpenShift Virtualization 2.6.0 security and bug fix update
- RHSA-2021:0516Red Hat Product SecurityMedium
Red Hat Security Advisory: Release of OpenShift Serverless 1.13.0 security update
Patch Availability(6)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | cryostat-20-tech-preview/cryostat-rhel8-operator:2.0.0-5 | 2021-12-14 | redhat |
| redhat | openshift4/ose-etcd:v4.8.0-202106152230.p0.git.aefa6bf.assembly.stream | 2021-07-27 | redhat |
| redhat | ocs4/mcg-rhel8-operator:5.7.0-69.85e2026.5.7 | 2021-05-19 | redhat |
| redhat | mcg-0:5.7.0-69.85e2026.5.7.el8 | 2021-05-19 | redhat |
| redhat | openshift4/ose-azure-machine-controllers:v4.7.0-202102130115.p0 | 2021-02-24 | redhat |
| redhat | openshift-serverless-1/svls-must-gather-rhel8:1.13.0-3 | 2021-02-18 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 3 ecosystems)
Go(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/dgrijalva/jwt-go | — |
| — |
| github.com/dgrijalva/jwt-go/v4 | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-dgrijalva-jwt-go | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-github-dgrijalva-jwt-go | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 7× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 166 total refreshes for this CVE.
- 2026-10-10 19:56 UTCEPSS rescore
- 2026-10-09 20:04 UTCEPSS rescore
- 2026-10-09 18:28 UTCOSV refresh
- 2026-10-08 16:38 UTCEPSS rescore
- 2026-10-07 23:44 UTCEPSS rescore
- 2026-10-06 15:13 UTCEPSS rescore
- 2026-10-05 17:39 UTCEPSS rescore
- 2026-10-03 14:22 UTCEPSS rescore
- 2026-09-30 15:16 UTCEG score recompute
- 2026-09-30 14:59 UTCEPSS rescore
- 2026-09-29 15:14 UTCEPSS rescore
- 2026-09-27 13:41 UTCEPSS rescore
- 2026-09-26 15:54 UTCEPSS rescore
- 2026-09-26 15:54 UTCEPSS rescore
- 2026-09-24 14:00 UTCEPSS rescore
- 2026-09-22 14:43 UTCEPSS rescore
- 2026-09-21 20:28 UTCEPSS rescore
- 2026-09-20 20:11 UTCEPSS rescore
- 2026-09-20 01:46 UTCOSV refresh
- 2026-09-19 15:37 UTCEPSS rescore
- 2026-09-18 19:23 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-16 14:04 UTCEPSS rescore
- 2026-09-15 03:06 UTCEPSS rescore
- 2026-09-13 16:43 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-12 14:57 UTCEPSS rescore
- 2026-09-11 09:32 UTCEPSS rescore
- 2026-09-08 21:56 UTCEPSS rescore
- 2026-09-07 15:57 UTCEPSS rescore
- 2026-09-06 13:44 UTCEPSS rescore
- 2026-09-05 15:24 UTCEPSS rescore
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 05:03 UTCEPSS rescore
- 2026-09-02 14:08 UTCEPSS rescore
- 2026-09-01 05:08 UTCOSV refresh
- 2026-09-01 03:32 UTCEPSS rescore
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-30 01:18 UTCEPSS rescore
- 2026-08-27 14:21 UTCEPSS rescore
- 2026-08-26 14:42 UTCEPSS rescore
- 2026-08-25 13:45 UTCEPSS rescore
- 2026-08-21 23:45 UTCEPSS rescore
- 2026-08-20 22:52 UTCEPSS rescore
- 2026-08-19 17:00 UTCEPSS rescore
- 2026-08-18 13:44 UTCEPSS rescore
- 2026-08-17 13:43 UTCEPSS rescore
- 2026-08-16 14:52 UTCEPSS rescore
- 2026-08-16 02:11 UTCEPSS rescore
- 2026-08-15 04:37 UTCOSV refresh
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-13 21:57 UTCEPSS rescore
- 2026-08-12 13:47 UTCEPSS rescore
- 2026-08-09 13:43 UTCEPSS rescore
- 2026-08-08 16:33 UTCEPSS rescore
- 2026-08-07 16:23 UTCEPSS rescore
- 2026-08-06 13:43 UTCEPSS rescore
- 2026-08-04 15:06 UTCEPSS rescore
- 2026-08-04 10:34 UTCEPSS rescore
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-08-01 04:12 UTCEPSS rescore
- 2026-07-30 16:51 UTCOSV refresh
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 01:27 UTCEPSS rescore
- 2026-07-28 15:33 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-24 14:14 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:51 UTCEG score recompute
- 2026-07-22 22:37 UTCEG score recompute
- 2026-07-22 14:05 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 01:57 UTCEPSS rescore
- 2026-07-13 22:27 UTCEPSS rescore
- 2026-07-13 22:27 UTCEPSS rescore
- 2026-07-13 06:10 UTCEPSS rescore
- 2026-07-13 06:10 UTCEPSS rescore
- 2026-07-13 02:07 UTCOSV refresh
- 2026-07-12 05:44 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-11 08:25 UTCEPSS rescore
- 2026-07-09 19:07 UTCEPSS rescore
- 2026-07-08 15:12 UTCEPSS rescore
- 2026-07-07 13:43 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 02:21 UTCEPSS rescore
- 2026-07-06 02:21 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat:RHSA-2020:5633 · redhat:RHSA-2021:2041 · redhat:RHSA-2021:2438
Frequently asked(5)
What is CVE-2020-26160?
When was CVE-2020-26160 disclosed?
Is CVE-2020-26160 actively exploited?
What is the CVSS score of CVE-2020-26160?
How do I remediate CVE-2020-26160?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-26160
Is Your Infrastructure Affected by CVE-2020-26160?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.