# CVE-2026-94265: Authorization: Negotiate sent to foreign 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-94265, BELL-CVE-2026-94265, CURL-CVE-2026-94265, DEBIAN-CVE-2026-94265, GHSA-qqmr-6r9w-pmx5, MINI-cvjf-rq6f-r9x9

## What is CVE-2026-94265?

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

### Official description

When processing an HTTP redirect to a URL containing userinfo (a
`username:password` component), curl might erroneously retain and re-transmit
the original host's HTTP Negotiate authentication state. Consequently, a
malicious server can trigger a redirect containing arbitrary userinfo to force
curl to send a freshly minted Kerberos ticket—generated using the ambient
identity of the client process to an untrusted third-party host, effectively
bypassing the domain-scoping restrictions normally enforced by the absence of
`--location-trusted`.

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


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

Upgrade to a fixed version.

## Is CVE-2026-94265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94265 is a vulnerability in curl, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94265 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-94265/ (Markdown: https://insights.sbomify.com/CVE-2026-94265/index.md)
```

## Sources

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

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