{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-88883 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-88883 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-88883 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-88883 in the wild and no public exploit code.\n\nAffected product: mend-renovate-ce. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-88883/ (Markdown: https://insights.sbomify.com/CVE-2026-88883/index.md)","id":"CVE-2026-88883","markdown":"https://insights.sbomify.com/CVE-2026-88883/index.md","name":"CVE-2026-88883","record":{"aliases":["GHSA-4hmw-qw74-vrhm","GHSA-qfw4-mmpc-67w5"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Renovate dependency tool","requires_auth":"low_privilege","summary":"Incomplete log sanitization allows attackers with log access to recover TLS private keys when Mutual TLS is configured without using the secrets feature.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Renovate before 44.14.4 TLS Private Key Log Sanitisation","id":"CVE-2026-88883","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Renovate before 44.3.1 Authentication Bypass via Digest Updates","id":"CVE-2026-88884"},"packages":[],"prev":{"headline":"Renovate before 44.11.2 Credential Exfiltration via Link Header","id":"CVE-2026-88882"},"products":["mend-renovate-ce","mend-renovate-enterprise-edition","renovate","renovate-ce","renovate-ee-server","renovate-ee-worker"],"published":"2026-09-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["mend","renovatebot"]},"summary":"Incomplete log sanitization allows attackers with log access to recover TLS private keys when Mutual TLS is configured without using the secrets feature.","url":"https://insights.sbomify.com/CVE-2026-88883/"}