Renovate vulnerable to Azure DevOps token leakage in logs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2020-37267: 0.43% estimated exploitation activity in the next 30 days; percentile 37.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

14 Sep 2020, 16:38 UTC

Last modified by the source

20 Oct 2026, 10:56 UTC

Source last checked

26 Oct 2026, 12:06 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-36rh-ggpr-j3gj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-36rh-ggpr-j3gj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-37267

Advisory: Renovate vulnerable to Azure DevOps token leakage in logs
IDs: CVE-2020-37267, GHSA-36rh-ggpr-j3gj
Record: https://patchnext.com/advisories/cve-2020-37267 (revision 2, source checked 26 Oct 2026, 12:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: renovate 23.25.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm renovate: affected >= 19.180.0, < 23.25.1; fixed in 23.25.1

## Suggested inspection (read-only)
- `npm ls renovate --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on renovate.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-36rh-ggpr-j3gj (OSV record GHSA-36rh-ggpr-j3gj lists affected ranges: npm renovate >=19.180.0 <23.25.1 (fixed))
- Verified: https://github.com/advisories/GHSA-36rh-ggpr-j3gj (GitHub-reviewed advisory GHSA-36rh-ggpr-j3gj lists affected ranges: npm renovate >=19.180.0 <23.25.1)

Commands are suggestions: review each one before running it.