BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2020
CVE-2020-26160High confidence

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)

Unknown · Unknown

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 2.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitygiteaVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.14.6-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communitygiteaVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.14.6-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.21v3.21 · communitygiteaVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.14.6-r0Alpine Security Database ↗Source updated 19 Aug 2026
Debian bookwormbookworm · sourcegolang-github-dgrijalva-jwt-goVendor fix publishedDebian records a fixed source-package version for this release.3.2.0-3Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-github-coreos-discovery-etcd-ioUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2020-26160 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjwt-go: access restriction bypass vulnerability
86 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kiali as a component of OpenShift Service Mesh 1
  • kiali.src as a component of OpenShift Service Mesh 1
  • servicemesh as a component of OpenShift Service Mesh 1
  • servicemesh-citadel as a component of OpenShift Service Mesh 1
  • servicemesh-galley as a component of OpenShift Service Mesh 1
  • servicemesh-istioctl as a component of OpenShift Service Mesh 1
  • servicemesh-mixc as a component of OpenShift Service Mesh 1
  • servicemesh-mixs as a component of OpenShift Service Mesh 1
  • servicemesh-operator as a component of OpenShift Service Mesh 1
  • servicemesh-operator.src as a component of OpenShift Service Mesh 1
  • servicemesh-pilot-agent as a component of OpenShift Service Mesh 1
  • servicemesh-pilot-discovery as a component of OpenShift Service Mesh 1
Summary
A vulnerability was found in jwt-go where it is vulnerable to Access Restriction Bypass if m["aud"] happens to be []string{}, as allowed by the spec, the type assertion fails and the value of aud is "". This can cause audience verification to succeed even if the audiences being passed are incorrect if required is set to false.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-1212

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Authentication → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-287 ↗

CWE-287: Improper Authentication. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.AVNetworkAttack vector: The vulnerable component can be reached over a network.ANoneAvailability impact: No direct loss is represented by this metric.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.PRNonePrivileges required: The attacker does not need an account or existing privileges.SUnchangedScope: The security impact remains within the vulnerable component's authority.UINoneUser interaction: No action by another user is required.
Post-exploitation / living off the land
Stolen credentials, tokens and legitimate administration functions may provide continued access without deploying a large custom toolset.
NetworkUnauthenticatedCWE-287
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2022-0510IBM DB2: Mehrere Schwachstellen

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM DB2 ausnutzen, um Dateien zu manipulieren, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, willkürlichen Code mit erhöhten Rechten auszuführen, Informationen falsch darzustellen und beliebigen Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20201007Security Bulletin 07 Oct 2020

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 07 Oct 2020, published on 7 October 2020. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-591Multiples vulnérabilités dans les produits IBM

d?id=CVE-2019-11840 Référence CVE CVE-2019-11841 https://www.cve.org/CVERecord?id=CVE-2019-11841 Référence CVE CVE-2019-16884 https://www.cve.org/CVERecord?id=CVE-2019-16884 Référence CVE CVE-2020-10752 https://www.cve.org/CVERecord?id=CVE-2020-10752 Référence CVE CVE-2020-14040 https://www.cve.org/CVERecord?id=CVE-2020-14040 Référence CVE CVE-2020-15106 https://www.cve.org/CVERecord?id=CVE-2020-15106 Référence CVE CVE-2020-15112 https://www.cve.org/CVERecord?id=CVE-2020-15112 Référence CVE CVE-2020-15113 https://www.cve.org/CVERecord?id=CVE-2020-15113 Référence CVE CVE-2020-25704 https://www.cve.org/CVERecord?id=CVE-2020-25704 Référence CVE CVE-2020-26160 https://www.cve.org/CVERecord?id=CVE-2020-26160 Référence CVE CVE-2020-27813 https://www.cve.org/CVERecord?id=CVE-2020-27813 Référence CVE CVE-2020-28851 https://www.cve.org/CVERecord?id=CVE-2020-28851 Référence CVE CVE-2020-28852 https://www.cve.org/CVERecord?id=CVE-2020-28852 Référence CVE CVE-2020-29368 https://www.cve.org/CVERecord?id=CVE-2020-29368 Référence CVE CVE-2020-29652 https://www.cve.org/CVERecord?id=CVE-2020-29652 Référence CVE CVE-2020-36067 https://www.cve.org/CVERecord?id=CVE-2020-36067 Référence CVE CVE-2020-36322 https://www.cve.org/CVERecord?id=CVE-2020-36322 Référence CVE CVE-2020-36385 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2020-012007jwt-go における認証に関する脆弱性

jwt-go には、認証に関する脆弱性、例外的な状態の処理に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 30 Sept 2020 · Last source change 4 Aug 2024, 15:49 UTC · CWE-287 · Improper Authentication

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-1212
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    n/a · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2021-1212↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2020-26160 · cve.blacktree.nl