CVE-2020-36569

CRITICALNVD 9.19.1—

9.1

Authentication is globally bypassed in github.com/nanobox-io/golang-nanoauth between v0.0.0-20160722212129-ac0cc4484ad4 and v0.0.0-20200131131040-063a3fb69896 if ListenAndServe is called with an empty token.

CVSS v3: 9.1
EG Score: 9.1(medium)
EPSS: 58.4%
KEV: Not listed

Published

December 27, 2022

Last Modified

April 11, 2025

References (6)

security@golanghttps://github.com/nanobox-io/golang-nanoauth/commit/063a3fb69896acf985759f0fe3851f15973993f3
security@golanghttps://github.com/nanobox-io/golang-nanoauth/pull/5
security@golanghttps://pkg.go.dev/vuln/GO-2020-0004
af854a3a-2127-422b-91ae-364da2661108https://github.com/nanobox-io/golang-nanoauth/commit/063a3fb69896acf985759f0fe3851f15973993f3
af854a3a-2127-422b-91ae-364da2661108https://github.com/nanobox-io/golang-nanoauth/pull/5
af854a3a-2127-422b-91ae-364da2661108https://pkg.go.dev/vuln/GO-2020-0004

Affected Packages

(1 across 1 ecosystem)

Go(1)

Package	Vulnerable range	Fixed in	Dependents
github.com/nanobox-io/golang-nanoauth	—	0.0.0-20200131131040-063a3fb69896	—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-287Improper Authentication

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-25 09:39 UTCEG score recompute

Frequently asked(5)

What is CVE-2020-36569?

CVE-2020-36569 is a critical vulnerability published on December 27, 2022. Authentication is globally bypassed in github.com/nanobox-io/golang-nanoauth between v0.0.0-20160722212129-ac0cc4484ad4 and v0.0.0-20200131131040-063a3fb69896 if ListenAndServe is called with an empty token.

When was CVE-2020-36569 disclosed?

CVE-2020-36569 was first published in the National Vulnerability Database on December 27, 2022, with the most recent update on April 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-36569 actively exploited?

CVE-2020-36569 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 58.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-36569?

CVE-2020-36569 has a CVSS v3 base score of 9.1 (NVD).

How do I remediate CVE-2020-36569?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-36569, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-36569

Explore →

Is Your Infrastructure Affected by CVE-2020-36569?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs