cve.bz

CVE-2026-86413 curl curl

9.1 criticalEPSS 0.7%

Critical (9.1) in curl curl. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.7% (unchanged from 0.7% a week ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-201 Insertion of Sensitive Information Into Sent Data
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-86413 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-86413?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-86413?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-86413 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
curlfrom 8.22.0 through 8.22.0
curlfrom 8.21.0 through 8.21.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14curl8.23.0~rc1-1DEBIAN-CVE-2026-86413
Red Hathummingbird:1curl, libcurl, libcurl-devel and 1 more0:8.23.0-0.1.hum1RHSA-2026:82895
SUSELinux Enterprise Module for Basesystem 15 SP7curl8.22.0-150700.7.33.1SUSE-SU-2026:5068-1
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6curl8.22.0-150600.4.58.1SUSE-SU-2026:5069-1
openSUSETumbleweedcurl8.23.0-1.1openSUSE-SU-2026:12150-1
Alpinev3.23, v3.24curl8.23.0-r0ALPINE-CVE-2026-86413
Alpaquita23, 25, streamcurl8.23.0-r0BELL-CVE-2026-86413
BellSoft Hardened Containersstreamcurl8.23.0-r0BELL-CVE-2026-86413

From the distributions' data via OSV.dev: the Debian Security Tracker; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Red Hat · SUSE · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Low.

Red Hat's statement

Red Hat rates this vulnerability as Low impact because successful credential exposure requires an uncommon combination of conditions: an HTTP request using Negotiate authentication with ambient Kerberos credentials must be configured to follow redirects to a secondary URL with embedded credentials. Furthermore, core Red Hat Enterprise Linux distributions ship curl versions outside the affected upstream release window. In typical enterprise environments, Kerberos-authenticated transfers rarely follow automated redirects across disparate origins, significantly limiting exposure in practice.

ProductPackageStateAdvisory
Red Hat Hardened Imagescurl-main-8.23.0-0.1.hum1Fixed 2026-10-14RHSA-2026:82895
Red Hat Enterprise Linux 10curlNot affected
Red Hat Enterprise Linux 10igvmNot affected
Red Hat Enterprise Linux 10rustNot affected
Red Hat Enterprise Linux 10s390utilsNot affected
Red Hat Enterprise Linux 10snphostNot affected
Red Hat Enterprise Linux 10trusteeNot affected
Red Hat Enterprise Linux 6curlNot affected
Red Hat Enterprise Linux 7curlNot affected
Red Hat Enterprise Linux 8curlNot affected
Red Hat Enterprise Linux 9curlNot affected
Red Hat Enterprise Linux 9rustNot affected
Red Hat Enterprise Linux 9snphostNot affected
Red Hat Hardened ImagesrustNot affected
Red Hat JBoss Core Servicesjbcs-httpd24-curlNot affected
Red Hat Satellite 6foremanNot affected
Red Hat Satellite 6openvox-agentNot affected
Red Hat Satellite 6puppet-agentNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-86413.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-618 Cellular Broadcast Message Request Severity: Low
  • CAPEC-619 Signal Strength Tracking Severity: Low
  • CAPEC-621 Analysis of Packet Timing and Sizes Severity: Low
  • CAPEC-622 Electromagnetic Side-Channel Attack Severity: Low
  • CAPEC-623 Compromising Emanations Attack Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON