Skip to content
Noroxi
CVE-2026-5545· NVD / CVE Program· CNA curl

wrong reuse of HTTP Negotiate connection

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: curl curl 33e43985b8f3b9e66691d06e70be0395849856cd, 8.14.2, 8.16.1.

Low priority for now. Upgrade to curl curl 33e43985b8f3b9e66691d06e70be0395849856cd, 8.14.2, 8.16.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1's and user2's credentials when it is in fact still using the connection authenticated for user1...

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
May 13, 2026
Updated
Sep 15, 2026
EPSS
0.5% · 42th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-5545

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for haxx records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
haxxcurl

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • haxx curl7.10.6 and later · before 8.20.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (curl). Independent of NVD's CPE analysis and usually ahead of it.

  • curl curl

    • 8.19.0, 8.18.0, 8.17.0, 8.16.0, 8.15.0, 8.14.1, 8.14.0, 8.13.0, 8.12.1, 8.12.0, 8.11.1, 8.11.0 … (+24)affected
    • 7.10.6 and later · before 8.14.2affected · semver
    • 8.15.0 and later · before 8.16.1affected · semver
    • 8.17.0 and later · before 8.20.0affected · semver
    • e56ae1426cb7a0a4a427cf8d6099a821fdaae428 and later · before 33e43985b8f3b9e66691d06e70be0395849856cdaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.22curlfrom 7.10.6 · before 8.14.1-r38.14.1-r3
Alpine:v3.23curlfrom 7.10.6 · before 8.20.0-r08.20.0-r0
Debian:12curlall versions—
Debian:13curlbefore 8.14.1-2+deb13u48.14.1-2+deb13u4
Debian:14curlbefore 8.20.0~rc2-18.20.0~rc2-1
openSUSE:Leap 16.0curlbefore 8.14.1-160000.6.18.14.1-160000.6.1
openSUSE:Tumbleweedcurlbefore 8.20.0-1.18.20.0-1.1
Red Hat:hummingbird:1curlbefore 0:8.20.0-0.1.hum10:8.20.0-0.1.hum1
Red Hat:hummingbird:1libcurlbefore 0:8.20.0-0.1.hum10:8.20.0-0.1.hum1
Red Hat:hummingbird:1libcurl-develbefore 0:8.20.0-0.1.hum10:8.20.0-0.1.hum1
Red Hat:hummingbird:1libcurl-minimalbefore 0:8.20.0-0.1.hum10:8.20.0-0.1.hum1
SUSE:Linux Enterprise Module for Basesystem 15 SP7curlbefore 8.14.1-150700.7.23.18.14.1-150700.7.23.1
SUSE:Linux Enterprise Server 16.0curl-minibefore 8.14.1-160000.6.18.14.1-160000.6.1
SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5curlbefore 8.0.1-11.123.18.0.1-11.123.1
SUSE:Linux Micro 6.2curlbefore 8.14.1-160000.6.18.14.1-160000.6.1

Same product

haxx: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t
    50Plan
  • CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
    47Plan
  • CVE-2024-2398HTTP/2 push headers memory-leak
    45Plan
  • CVE-2019-5482Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
    44Plan
  • CVE-2017-8817The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and app
    42Plan
  • CVE-2017-8816The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer
    42Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
curl curl33e43985b8f3b9e66691d06e70be0395849856cdVendor (CNA)
curl curl8.14.2Vendor (CNA)
curl curl8.16.1Vendor (CNA)
curl curl8.20.0Vendor (CNA)
alpine:curl8.14.1-r3 · Alpine:v3.22Package registry (OSV)
debian:curl8.14.1-2+deb13u4 · Debian:13Package registry (OSV)
opensuse:curl8.20.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:curl0:8.20.0-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:libcurl0:8.20.0-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:libcurl-devel0:8.20.0-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:libcurl-minimal0:8.20.0-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:curl8.14.1-160000.6.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:curl-mini8.14.1-160000.6.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-893251 days apartincomplete mTLS config matching in conn reuse
    30Monitor
  • CVE-2026-196563 days apartbad reuse of HTTP Negotiate connection
    26Monitor
  • CVE-2026-378463 days apartwrong proxy connection reuse with credentials
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-305 · Authentication Bypass by Primary Weakness

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records