Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

GHSA-v7x3-7hw7-pcjg

MEDIUM

GHSA-v7x3-7hw7-pcjg is a medium-severity (CVSS 5.3) vulnerability in renovate. O3 Security confirms whether GHSA-v7x3-7hw7-pcjg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Renovate vulnerable to leakage of temporary repository tokens into Pull Request comments

Published
Oct 21, 2019
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
375Kdownloads / week

Description

Impact

Temporary repository tokens were leaked into Pull Requests comments in during certain Go Modules update failure scenarios.

Patches

The problem has been patched. Self-hosted users should upgrade to v19.38.7 or later.

Workarounds

Disable Go Modules support.

References

Blog post: https://renovatebot.com/blog/go-modules-vulnerability-disclosure

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmrenovate13.87.0&&< 19.38.719.38.7

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for renovate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update renovate to 19.38.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v7x3-7hw7-pcjg is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-v7x3-7hw7-pcjg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v7x3-7hw7-pcjg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Temporary repository tokens were leaked into Pull Requests comments in during certain Go Modules update failure scenarios. ### Patches The problem has been patched. Self-hosted users should upgrade to v19.38.7 or later. ### Workarounds Disable Go Modules support. ### References Blog post: https://renovatebot.com/blog/go-modules-vulnerability-disclosure ### For more information If you have any questions or comments about this advisory: * Open an issue in [Renovate](http://github.com/renovatebot/renovate)
O3 Security · Impact-Aware SCA

Is GHSA-v7x3-7hw7-pcjg in your dependencies?

O3 detects GHSA-v7x3-7hw7-pcjg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-v7x3-7hw7-pcjg: renovate (Medium 5.3) | O3 Security