{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-88884 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-88884 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-88884 is a medium-severity vulnerability in mend-renovate-ce, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-88884 and fix it if it is affected.\n\nWhat it is: CVE-2026-88884 is a medium-severity vulnerability in mend-renovate-ce, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-88884 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-88884/ (Markdown: https://insights.sbomify.com/CVE-2026-88884/index.md)","id":"CVE-2026-88884","markdown":"https://insights.sbomify.com/CVE-2026-88884/index.md","name":"CVE-2026-88884","record":{"aliases":["GHSA-g4qr-hw2h-687r","GHSA-x9q2-x5p7-v69h"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Renovate dependency tool","requires_auth":"none","summary":"Attackers can bypass minimum release age checks for digest updates, causing malicious dependencies to trigger CI workflows prematurely in Renovate.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Renovate is a dependency update automation tool. In versions before 44.3.1 (and Mend Renovate CE/EE images before 15.4.0, mend-renovate-ce Helm chart before 15.4.0, mend-renovate-enterprise-edition Helm chart before 10.4.0), digest updates are not subject to the internal `minimumReleaseAge` (stability age) checks. When a repository configures `minimumReleaseAge` and has dependencies with `updateType=digest` — for example GitHub Actions pinned to a commit SHA with a floating tag, Docker images, Go modules or NuGet packages — Renovate will still open a pull request for a newly published digest, marked only with a pending `renovate/stability-days` status check. A newly published, potentially malicious dependency version can therefore cause a PR to be raised and CI workflows to potentially run before the configured minimum release age has elapsed, which is precisely what the Minimum Release Age control is intended to prevent. The issue is fixed in Renovate 44.3.1; as a workaround, digest updates can be disabled or gated behind `dependencyDashboardApproval`.","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.3.1 Authentication Bypass via Digest Updates","id":"CVE-2026-88884","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Renovate before 44.14.7 Command Injection via depName","id":"CVE-2026-88885"},"packages":[],"prev":{"headline":"Renovate before 44.14.4 TLS Private Key Log Sanitisation","id":"CVE-2026-88883"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["mend","renovatebot"]},"summary":"Attackers can bypass minimum release age checks for digest updates, causing malicious dependencies to trigger CI workflows prematurely in Renovate.","url":"https://insights.sbomify.com/CVE-2026-88884/"}