Skip to content
Applications

CVE-2019-25766

8.7
High
EPSS 0.31%Patch availableAug 19, 2026

Renovate leaked temporary repo tokens in PR comments (fixed in 19.38.7).

common questions

Is CVE-2019-25766 being exploited?

Not confirmed. CVE-2019-25766 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.

How severe is CVE-2019-25766?

CVE-2019-25766 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2019-25766?

Yes. A fix has been recorded for CVE-2019-25766. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2019-25766 affect?

CVE-2019-25766 affects Renovate >=13.87.0 and <=19.38.6, Repositories using Renovate, Pull request comments (where tokens were leaked). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2019-25766?

Upgrade to Renovate 19.38.7 and rotate any exposed tokens immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Renovate >=13.87.0 and <=19.38.6Repositories using RenovatePull request comments (where tokens were leaked)
impact

Temporary repository tokens were exposed in pull-request comments; viewers can steal tokens to access, modify, or abuse repositories and CI.

action required

Patch when possible

affected versions
renovatebot renovate
  • affected>= 13.87.0 and < 19.38.7
vendor says fixed in19.38.7

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free