# CVE-2026-88880: Renovate before 44.11.3 Credential Exfiltration via Link Header

> Attackers can exfiltrate authentication credentials by manipulating Link headers in GitLab pagination responses, affecting Renovate users.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-9hmg-9h89-jhmx, GHSA-wqcg-39wp-gpqc

## What is CVE-2026-88880?

CVE-2026-88880 is a critical 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.

### Official description

Renovate before 44.11.3 fails to validate Link header destinations when following GitLab server pagination, allowing malicious servers to redirect credential-bearing requests. Attackers controlling a compromised GitLab server can specify a Link header pointing to attacker-controlled infrastructure to exfiltrate authentication credentials.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2026-88880 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88880 is a critical 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.
Exploitation: There is no known exploitation of CVE-2026-88880 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-88880/ (Markdown: https://insights.sbomify.com/CVE-2026-88880/index.md)
```

## Sources

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

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