Renovate vulnerable to Azure DevOps token leakage in logs
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### 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.
Why it matters now
Fix Fixed renovate (npm): 23.25.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | renovate (npm) | 19.180.0 to before 23.25.1 | 23.25.1 | Patch available | GHSA-36rh-ggpr-j3gj |
- renovate (npm) Vendor— Affected 19.180.0 to before 23.25.1 Fixed in 23.25.1 Patch available GHSA-36rh-ggpr-j3gj
Remediation
- Fix · GHSA-36rh-ggpr-j3gj renovate (npm) Fixed in 23.25.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-36rh-ggpr-j3gj
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences