CVE-2026-88884: Renovate before 44.3.1 Authentication Bypass via Digest Updates
Renovate is a dependency update automation tool. In versions before 44.3.1 (and Mend Renovate CE/EE images before 15.4.0, mend-renovate-ce Helm chart before 15.4.0, mend-renovate-enterprise-edition Helm chart before 10.4.0), digest updates are not subject to the internal minimumReleaseAge (stability age) checks. When a repository configures minimumReleaseAge and has dependencies with updateType=digest — for example GitHub Actions pinned to a commit SHA with a floating tag, Docker images, Go modules or NuGet packages — Renovate will still open a pull request for a newly published digest, marked only with a pending renovate/stability-days status check. A newly published, potentially malicious dependency version can therefore cause a PR to be raised and CI workflows to potentially run before the configured minimum release age has elapsed, which is precisely what the Minimum Release Age control is intended to prevent. The issue is fixed in Renovate 44.3.1; as a workaround, digest updates can be disabled or gated behind dependencyDashboardApproval.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Renovateto a version that resolves this vulnerability.Fixed in 44.3.1 - Configuration
As a workaround for versions before 44.3.1, gate digest updates behind `dependencyDashboardApproval` (i.e., require dashboard approval) so digest updates do not create PRs that bypass `minimumReleaseAge` checks.
Renovate dependencyDashboardApproval = enable gating for digest updates - Configuration
As a workaround for versions before 44.3.1, disable digest updates so Renovate does not open PRs for newly published digest versions that bypass internal `minimumReleaseAge` checks.
Renovate updateType=digest = disabled (workaround)
Event History
Frequently Asked Questions
Which dependency updates can bypass the configured stability-age control?
Digest updates are affected when minimumReleaseAge is configured. Examples include GitHub Actions pinned to a commit SHA with a floating tag, Docker images, Go modules, and NuGet packages.
What must happen for this issue to create risk in a repository?
The repository must use minimumReleaseAge and have dependencies updated with updateType=digest. A newly published digest can then cause Renovate to open a pull request before the configured age has elapsed, and CI workflows may run for that PR.
Are the affected pull requests visibly identified as not having completed the stability period?
Yes. Renovate marks the pull request with a pending renovate/stability-days status check, but still opens the pull request before the minimum release age is reached.
What can be done if upgrading is not immediately possible?
Disable digest updates, or require dependencyDashboardApproval before digest-update pull requests proceed. These workarounds prevent or gate the early pull requests.
Which versions contain the fix?
The issue is fixed in Renovate 44.3.1, Mend Renovate CE/EE images 15.4.0, the mend-renovate-ce Helm chart 15.4.0, and the mend-renovate-enterprise-edition Helm chart 10.4.0.