# CVE-2026-86413: Negotiate credentials sent to redirected origin


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** ALPINE-CVE-2026-86413, BELL-CVE-2026-86413, CURL-CVE-2026-86413, DEBIAN-CVE-2026-86413, GHSA-x2p4-rxj5-99w6, MINI-pxh8-xp88-8mvf

## What is CVE-2026-86413?

CVE-2026-86413 is a vulnerability in curl, published on 20 Oct 2026. 

### Official description

When using an *ambient user* in a first transfer doing Negotiate
authentication and asked to follow redirects, curl could pass on its
credential details to an unrelated second origin when asked to redirect there.

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


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

Upgrade to a fixed version.

## Is CVE-2026-86413 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86413 is a vulnerability in curl, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-86413 in the wild and no public exploit code.

Affected product: curl. 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-86413/ (Markdown: https://insights.sbomify.com/CVE-2026-86413/index.md)
```

## Sources

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

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