External risk intelligence

Renovate Credential Leakage Via Malicious Container Registry Link Header

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-88887

Renovate is a developer-focused dependency automation tool typically run in isolated build environments, CI/CD pipelines, or internal orchestration systems. It is not an internet-facing service, edge gateway, or public-facing portal, and its function is to perform background tasks within a secured development ecosystem.

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Renovate, a tool that automates dependency updates for software development. The issue could allow a malicious or compromised container registry to intercept credentials used by Renovate if it interacts with such a registry. The primary concern at this stage is to confirm if your organization uses Renovate with container dependencies that might interact with external registries.

  • Malicious registries can steal tool credentials.
  • Important for teams managing container dependencies.
  • Verify Renovate usage with container dependencies.

Attack Path

How an attacker could exploit the issue

An attacker could trick Renovate into sending sensitive registry credentials to a malicious server. This happens when Renovate fetches information about container image tags or digests from a registry. If the registry is compromised or malicious, it can send a specially crafted "Link" header in its response. This header can redirect Renovate to a different, attacker-controlled location, causing it to send the registry's credentials to that location.

  • Requires interaction with a malicious registry.
  • Trickery via crafted Link header.
  • Risk of credential exfiltration.

Live Threat

Current exploitation, exposure, and threat context

Renovate could expose registry credentials when processing container image tags or digests from a malicious or compromised registry. This occurs when Renovate follows pagination links provided in the HTTP Link header to an attacker-controlled host, and the registry's response includes the credentials. This risk is present when the affected system uses container dependencies and interacts with a compromised registry.

  • Registry credentials could be exposed.
  • Malicious registry redirects pagination links.
  • Unauthorized access to registry credentials.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in Renovate could lead to credential exfiltration if a compromised or malicious container registry is used. Teams responsible for development pipelines, CI/CD tooling, and platform operations should prioritize confirming exposure and planning remediation. The first practical step is to identify all Renovate instances, assess their interaction with container registries, and determine if they are configured to follow pagination links.

  • Identify Renovate instances and registry interactions.
  • Confirm exposure to malicious registries.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Renovate and why is it used?

Renovate is an automated dependency management tool designed for software developers. It scans project configuration files to detect outdated software libraries and container images, automatically creating pull requests to update them. It is widely used within development workflows, CI/CD pipelines, and internal build systems to maintain software security and keep dependencies current by automating the tedious process of tracking and patching package versions.

How does CVE-2026-88887 work in plain English?

This vulnerability is classified as a URL Redirection to Untrusted Site, or Open Redirect (CWE-601). The flaw exists in how Renovate handles pagination links during container registry lookups. When fetching image data, the tool blindly follows redirection links provided by the registry. If a registry is malicious, it can supply a link pointing to an attacker-controlled server, tricking Renovate into sending its authentication credentials for that registry to the attacker.

Does interacting with any registry trigger the bug?

No. The vulnerability is not triggered by standard, trusted registries. An attacker must successfully influence the pagination process, which requires Renovate to be actively interacting with a registry that is either malicious from the start or has been compromised. If Renovate is not configured to fetch container dependencies, or if it is only interacting with secure, trusted, and verified internal registries, this specific redirection path is not active.

Is my Renovate instance at high risk?

Halo Surface Signal indicates that Renovate is typically deployed in isolated CI/CD or internal development environments, making it a very unlikely candidate for internet-facing exposure. While the vulnerability is technically critical, the risk is localized to teams that use Renovate to fetch container images from untrusted or third-party registries. You should focus on whether your Renovate configurations involve fetching packages from sources outside your controlled infrastructure.

What should I do to secure my Renovate installation?

The most effective response is to update Renovate to the latest patched version (44.11.2 or later). If you cannot update immediately, identify where your Renovate instances are fetching container dependencies and verify those registries. You can also temporarily disable cross-origin pagination by setting the environment variable RENOVATE_X_DOCKER_PAGINATION_ALLOW_CROSS_ORIGIN to false, which prevents the tool from following the dangerous redirection links.

References