Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-5545— wrong reuse of HTTP Negotiate connection

AI Predicted 5.3 Difficulty: Easy EPSS 0.05% · P16

Possible ATT&CK Techniques 1AI

T1078 · Valid Accounts

Affected Version Matrix 171

VendorProductVersion RangeStatus
curlcurl8.19.0≤ 8.19.0affected
8.18.0≤ 8.18.0affected
8.17.0≤ 8.17.0affected
8.16.0≤ 8.16.0affected
8.15.0≤ 8.15.0affected
8.14.1≤ 8.14.1affected
8.14.0≤ 8.14.0affected
8.13.0≤ 8.13.0affected
… +163 more rows
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-5545

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
wrong reuse of HTTP Negotiate connection
Source: NVD (National Vulnerability Database)
Vulnerability Description
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...
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
libcurl 代码问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
libcurl是cURL开源的一个免费且易于使用的客户端 URL 传输库。 libcurl存在代码问题漏洞,该漏洞源于连接重用逻辑错误,可能导致在Negotiate认证后错误地重用使用不同凭据的现有连接。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
curlcurl 8.19.0 ~ 8.19.0 -

II. Public POCs for CVE-2026-5545

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-5545

登录查看更多情报信息。

Same Patch Batch · curl · 2026-05-13 · 8 CVEs total

CVE-2026-7168cross-proxy Digest auth state leak
CVE-2026-7009OCSP stapling bypass with Apple SecTrust
CVE-2026-6253proxy credentials leak over redirect-to proxy
CVE-2026-6429netrc credential leak with reused proxy connection
CVE-2026-6276stale custom cookie host causes cookie leak
CVE-2026-4873connection reuse ignores TLS requirement
CVE-2026-5773wrong reuse of SMB connection

IV. Related Vulnerabilities

V. Comments for CVE-2026-5545

No comments yet


Leave a comment