How severe is GHSA-36rh-ggpr-j3gj?

No CVSS score has been assigned to GHSA-36rh-ggpr-j3gj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-36rh-ggpr-j3gj?

GHSA-36rh-ggpr-j3gj affects the following packages: renovate (npm). Ecosystems affected: npm.

How do I fix GHSA-36rh-ggpr-j3gj?

Update renovate to 23.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-36rh-ggpr-j3gj is resolved across your whole dependency graph.

How do I detect GHSA-36rh-ggpr-j3gj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for renovate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-36rh-ggpr-j3gj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-36rh-ggpr-j3gj actively exploited in the wild?

No public exploit code has been indexed for GHSA-36rh-ggpr-j3gj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-36rh-ggpr-j3gj published, and has it been updated?

GHSA-36rh-ggpr-j3gj was published on September 14, 2020 and was last updated on August 11, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Renovate vulnerable to Azure DevOps token leakage in logsGHSA-36rh-ggpr-j3gj

GHSA-36rh-ggpr-j3gj is a security vulnerability in renovate. A fix is available for renovate — see the affected versions and patch details below.

Published

Sep 14, 2020

Updated

Aug 11, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 11, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

14other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

renovatenpm

407Kdownloads / week

Description

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`renovate`	≥ 19.180.0&&< 23.25.1	23.25.1`npm install renovate@23.25.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for renovate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update renovate to 23.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-36rh-ggpr-j3gj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-36rh-ggpr-j3gj in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works