# CVE-2026-88883: Renovate before 44.14.4 TLS Private Key Log Sanitisation

> Incomplete log sanitization allows attackers with log access to recover TLS private keys when Mutual TLS is configured without using the secrets feature.

- **Severity:** High 8.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-4hmw-qw74-vrhm, GHSA-qfw4-mmpc-67w5

## What is CVE-2026-88883?

CVE-2026-88883 is a high-severity vulnerability in mend-renovate-ce, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-88883?


## How do I fix CVE-2026-88883?

No fix has been published for CVE-2026-88883 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88883 being exploited?

There is no known exploitation of CVE-2026-88883 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88883 and fix it if it is affected.

What it is: CVE-2026-88883 is a high-severity vulnerability in mend-renovate-ce, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88883 in the wild and no public exploit code.

Affected product: mend-renovate-ce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88883/ (Markdown: https://insights.sbomify.com/CVE-2026-88883/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88883
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88883
- OSV: https://osv.dev/vulnerability/CVE-2026-88883

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88883/
Summaries are generated and may contain mistakes; the official description above is the record.