CVE-2026-88883
Description
A flaw was found in Renovate, an automated dependency update tool. Due to incomplete log sanitization, Transport Layer Security (TLS) private keys used for Mutual TLS could be written to logs in cleartext. This occurs when these keys are configured in a specific way without utilizing the documented secrets configuration. An attacker with access to these logs could recover the private key, leading to sensitive information disclosure.
Statement
Moderate: This flaw in Renovate, as deployed in Red Hat Konflux, allows for information disclosure of TLS private keys. When Mutual TLS is configured using hostRules[].httpsPrivateKey without utilizing the secrets configuration, private keys are written in cleartext to Renovate's logs. This could enable an attacker with local log access to recover sensitive key material.
Mitigation
To mitigate this issue, ensure that TLS private keys for Mutual TLS in Renovate configurations are always supplied via the documented `secrets` mechanism. Avoid directly embedding private keys within the `hostRules[].httpsPrivateKey` field. Refer to Renovate's official documentation for proper `secrets` configuration to prevent cleartext logging of sensitive key material.
Understanding the Weakness (CWE)
Integrity,Confidentiality,Availability,Non-Repudiation
Technical Impact: Modify Application Data; Hide Activities; Execute Unauthorized Code or Commands
Interpretation of the log files may be hindered or misdirected if an attacker can supply data to the application that is subsequently logged verbatim. In the most benign case, an attacker may be able to insert false entries into the log file by providing the application with input that includes appropriate characters. Forged or otherwise corrupted log files can be used to cover an attacker's tracks, possibly by skewing statistics, or even to implicate another party in the commission of a malicious act. If the log file is processed automatically, the attacker can render the file unusable by corrupting the format of the file or injecting unexpected characters. An attacker may inject code or other commands into the log file and take advantage of a vulnerability in the log processing utility.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
