Renovate vulnerable to Azure DevOps token leakage in logs
Impact
Applies to Azure DevOps users only. The bot's token may be exposed in server or pipeline logs due to the http.extraheader=AUTHORIZATION parameter being logged without redaction. It is recommended that Azure DevOps users revoke their existing bot credentials and generate new ones after upgrading if there's a potential that logs have been saved to a location that others can view.
Patches
Fixed in
Workarounds
Do not share Renovate logs with anyone who cannot be trusted with access to the token.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | renovate | >= 19.180.0, < 23.25.1 | 23.25.1 |
References
- Weakness (CWE)
-- Platform
- npm
- Package
renovate- Disclosed
- 14.09.2020
- Updated
- 20.10.2026 13:17
Sources and licenses
OSV / GitHub Advisory Database - GHSA-36rh-ggpr-j3gj - CC BY 4.0
Vulnerability history: renovate
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 11
- First → latest
- 10.2019 04.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Medium 11
Disclosures per year
- 2019: 1
- 2020: 1
- 2021: 0
- 2022: 0
- 2023: 0
- 2024: 1
- 2025: 0
- 2026: 8
-
Renovate vulnerable to Azure DevOps token leakage in logs this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.