Renovate versions >=19.180.0 and <23.25.1, when used with Azure DevOps, may expose the bot's authorization token in server or pipeline logs because the git http.extraheader=AUTHORIZATION parameter is logged without redaction. Anyone with access to saved logs could obtain the bot credentials. Fixed in 23.25.1; Azure DevOps users should revoke and regenerate credentials if logs may have been exposed.
CVE-2020-37267
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
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%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Renovate 19.180.0 before 23.25.1 Token Leakage via Logs | Advisories | VulnCheck
https://www.vulncheck.com/advisories/renovate-before-token-leakage-via-logsAzure DevOps token leakage in logs · Advisory · renovatebot/renovate · GitHub
https://github.com/renovatebot/renovate/security/advisories/GHSA-36rh-ggpr-j3gjVendor Advisories for CVE-2020-37267(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× 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.
- 2026-08-21 02:38 UTCEG score recompute
- 2026-08-21 02:38 UTCGHSA enrichment
- 2026-08-20 22:52 UTCEPSS rescore
- 2026-08-20 15:14 UTCGHSA enrichment
- 2026-08-20 03:50 UTCGHSA enrichment
- 2026-08-19 16:25 UTCEG score recompute
- 2026-08-19 16:25 UTCGHSA enrichment
- 2026-08-19 15:38 UTCEG score recompute
- 2026-08-19 15:38 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 14:13 UTCEG score recompute
- 2026-08-19 14:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS p95CRITICAL
- CVE-2018-11716EG 9.8EPSS p96CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8CRITICAL
- CVE-2018-1117NVD 5.0EG 9.8CRITICAL
- CVE-2018-11320EG 9.8CRITICAL
- CVE-2018-1000123EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2020-37267?
When was CVE-2020-37267 disclosed?
Is CVE-2020-37267 actively exploited?
What is the CVSS score of CVE-2020-37267?
How do I remediate CVE-2020-37267?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2020-37267
Is Your Infrastructure Affected by CVE-2020-37267?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.