Description
Renovate is an automated dependency update tool. In versions before 44.14.4 (and Mend Renovate CE/EE images before 15.4.0 and the mend-renovate-enterprise-edition Helm chart before 10.4.0), log sanitisation for TLS private keys used for Mutual TLS was incomplete. While the value of hostRules[].httpsPrivateKey was redacted in the field itself, the same private key value was not redacted if it also appeared elsewhere — for example in another configuration option or in a log message under a key other than httpsPrivateKey — causing the full private key to be written to Renovate's logs in cleartext. This affects deployments that configure Mutual TLS through hostRules[].httpsPrivateKey without passing the value through the documented `secrets` configuration. Anyone able to read the resulting logs can recover the private key. The issue is fixed in Renovate 44.14.4, which redacts any value supplied as hostRules[].httpsPrivateKey wherever it appears in the logs; as a workaround, supply the key via the `secrets` configuration.
Published: 2026-09-10
Score: 8.3 High
EPSS: n/a
KEV: No
Impact: Log Exposure of Private TLS Keys
Action: Update
AI Analysis

Impact

The vulnerability allows an actor with read access to Renovate logs to retrieve TLS private keys that are used for mutual authentication. The implementation flaw results in incomplete redaction of the hostRules[].httpsPrivateKey value when it is referenced elsewhere in configuration or log messages, leaving the full key in plaintext. The exposed key could be used to impersonate the service, gain unauthorized access, or compromise future connections. This flaw is a classic example of log injection and improper sanitisation, corresponding to CWE-532.

Affected Systems

The affected product is Renovate, the automated dependency update tool produced by renovatebot. Versions earlier than 44.14.4 are impacted, as are Mend‑Renovate CE/EE Docker images below version 15.4.0 and the mend-renovate‑enterprise‑edition Helm chart prior to 10.4.0. Any deployment that configures the httpsPrivateKey in hostRules[].httpsPrivateKey without delivering it through the documented secrets configuration is vulnerable.

Risk and Exploitability

The CVSS score of 8.3 indicates a high impact and moderate to high likelihood of exploitation. Although the EPSS score is not available, the vulnerability is not listed in CISA’s KEV catalogue, suggesting that no widespread exploit is currently confirmed. The most likely attack vector requires local or remote log reading; an attacker who can access the log files can extract the private key and use it to forge TLS connections. Protection of log access and applying the patch are essential to mitigate risk.

Generated by OpenCVE AI on September 10, 2026 at 14:57 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Renovate to version 44.14.4 or later, and update Mend Renovate images to 15.4.0 or later and Helm chart to 10.4.0 or later.
  • If immediate upgrade is not possible, configure TLS private keys through the secrets configuration instead of hostRules[].httpsPrivateKey to trigger proper log sanitisation.
  • Restrict read access to Renovate log files and ensure that logs do not expose private key material; periodically audit logs for unintended key disclosure.

Generated by OpenCVE AI on September 10, 2026 at 14:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 10 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 10 Sep 2026 13:30:00 +0000

Type Values Removed Values Added
Description Renovate is an automated dependency update tool. In versions before 44.14.4 (and Mend Renovate CE/EE images before 15.4.0 and the mend-renovate-enterprise-edition Helm chart before 10.4.0), log sanitisation for TLS private keys used for Mutual TLS was incomplete. While the value of hostRules[].httpsPrivateKey was redacted in the field itself, the same private key value was not redacted if it also appeared elsewhere — for example in another configuration option or in a log message under a key other than httpsPrivateKey — causing the full private key to be written to Renovate's logs in cleartext. This affects deployments that configure Mutual TLS through hostRules[].httpsPrivateKey without passing the value through the documented `secrets` configuration. Anyone able to read the resulting logs can recover the private key. The issue is fixed in Renovate 44.14.4, which redacts any value supplied as hostRules[].httpsPrivateKey wherever it appears in the logs; as a workaround, supply the key via the `secrets` configuration.
Title Renovate before 44.14.4 TLS Private Key Log Sanitisation
Weaknesses CWE-532
References
Metrics cvssV3_1

{'score': 7.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N'}

cvssV4_0

{'score': 8.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-10T14:55:53.845Z

Reserved: 2026-09-10T11:25:34.912Z

Link: CVE-2026-88883

cve-icon Vulnrichment

Updated: 2026-09-10T14:18:27.262Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-10T14:17:16.997

Modified: 2026-09-10T15:17:58.213

Link: CVE-2026-88883

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-10T15:00:15Z

Weaknesses
  • CWE-532

    Insertion of Sensitive Information into Log File