CVE-2026-5545-curl-AtomGit

已关闭

CVE-2026-5545 #199

openLiBingCI创建于 4月29日关闭于 5月19日

4月29日创建

一、漏洞信息
漏洞编号：CVE-2026-5545
漏洞归属组件：curl
漏洞归属的版本：7.71.1,7.77.0,7.79.1,7.86.0,8.1.2,8.20.0,8.4.0
CVSS评分：
BaseScore：6.5 Medium
Vector：CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
漏洞简述：
libcurl might in some circumstances reuse the wrong connection when asked todo an authenticated HTTP(S) request after a Negotiate-authenticated one, whenboth use the same host.libcurl features a pool of recent connections so that subsequent requests canreuse an existing connection to avoid overhead.When reusing a connection a range of criteria must be met. Due to a logicalerror in the code, a request that was issued by an application couldwrongfully reuse an existing connection to the same server that wasauthenticated using different credentials.An application that first uses Negotiate authentication to a server withuser1:password1 and then does another operation to the same server askingfor any authentication method but for user2:password2 (while the previousconnection is still alive) - the second request gets confused and wronglyreuses the same connection and sends the new request over that connectionthinking it uses a mix of user1 s and user2 s credentials when it is in factstill using the connection authenticated for user1...
漏洞公开时间：2026-05-13 21:01:56
漏洞创建时间：2026-04-29 17:42:00
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-5545

更多参考(点击展开)

参考来源	参考链接	来源链接
	https://curl.se/docs/CVE-2026-5545.json
	https://nvd.nist.gov/vuln/detail/CVE-2026-5545
	https://curl.se/docs/CVE-2026-5545.html
	https://hackerone.com/reports/3642555
	https://bugzilla.redhat.com/show_bug.cgi?id=2461204
	https://www.cve.org/CVERecord?id=CVE-2026-5545
	https://seclists.org/oss-sec/2026/q2/266

漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息：

详情(点击展开)

无

二、漏洞分析结构反馈
影响性分析说明：
libcurl might in some circumstances reuse the wrong connection when asked todo an authenticated HTTP(S) request after a Negotiate-authenticated one, whenboth use the same host.libcurl features a pool of recent connections so that subsequent requests canreuse an existing connection to avoid overhead.When reusing a connection a range of criteria must be met. Due to a logicalerror in the code, a request that was issued by an application couldwrongfully reuse an existing connection to the same server that wasauthenticated using different credentials.An application that first uses Negotiate authentication to a server withuser1:password1 and then does another operation to the same server askingfor any authentication method but for user2:password2 (while the previousconnection is still alive) - the second request gets confused and wronglyreuses the same connection and sends the new request over that connectionthinking it uses a mix of user1 s and user2 s credentials when it is in factstill using the connection authenticated for user1...
openEuler评分：
6.5
Vector：CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
受影响版本排查(受影响/不受影响)：
1.master(8.20.0):不受影响
2.openEuler-20.03-LTS-SP4(7.71.1):受影响
3.openEuler-22.03-LTS-SP4(7.79.1):受影响
4.openEuler-24.03-LTS(8.4.0):受影响
5.openEuler-24.03-LTS-Next(8.4.0):受影响
6.openEuler-24.03-LTS-SP1(8.4.0):受影响
7.openEuler-24.03-LTS-SP3(8.4.0):受影响
8.openEuler-24.03-LTS-SP4(8.4.0):受影响

修复是否涉及abi变化(是/否)：
1.master(8.20.0):否
2.openEuler-20.03-LTS-SP4(7.71.1):否
3.openEuler-22.03-LTS-SP4(7.79.1):否
4.openEuler-24.03-LTS(8.4.0):否
5.openEuler-24.03-LTS-Next(8.4.0):否
6.openEuler-24.03-LTS-SP1(8.4.0):否
7.openEuler-24.03-LTS-SP3(8.4.0):否
8.openEuler-24.03-LTS-SP4(8.4.0):否

原因说明：
1.master(8.20.0):不受影响-已有内置的内联控制或缓解措施
2.openEuler-20.03-LTS-SP4(7.71.1):正常修复
3.openEuler-22.03-LTS-SP4(7.79.1):正常修复
4.openEuler-24.03-LTS(8.4.0):正常修复
5.openEuler-24.03-LTS-Next(8.4.0):正常修复
6.openEuler-24.03-LTS-SP1(8.4.0):正常修复
7.openEuler-24.03-LTS-SP3(8.4.0):正常修复
8.openEuler-24.03-LTS-SP4(8.4.0):正常修复

O openLiBingCI成员

4月29日添加了label：CVE/UNFIXED

openeuler-ci-bot成员

4月29日评论：

issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(8.4.0):
2.openEuler-20.03-LTS-SP4(7.71.1):
3.openEuler-22.03-LTS-SP4(7.79.1):
4.openEuler-24.03-LTS(8.4.0):
5.openEuler-24.03-LTS-Next(8.4.0):
6.openEuler-24.03-LTS-SP1(8.4.0):
7.openEuler-24.03-LTS-SP3(8.4.0):
8.openEuler-24.03-LTS-SP4(8.4.0):

修复是否涉及abi变化(是/否)：
1.master(8.4.0):
2.openEuler-20.03-LTS-SP4(7.71.1):
3.openEuler-22.03-LTS-SP4(7.79.1):
4.openEuler-24.03-LTS(8.4.0):
5.openEuler-24.03-LTS-Next(8.4.0):
6.openEuler-24.03-LTS-SP1(8.4.0):
7.openEuler-24.03-LTS-SP3(8.4.0):
8.openEuler-24.03-LTS-SP4(8.4.0):

原因说明：
1.master(8.4.0):
2.openEuler-20.03-LTS-SP4(7.71.1):
3.openEuler-22.03-LTS-SP4(7.79.1):
4.openEuler-24.03-LTS(8.4.0):
5.openEuler-24.03-LTS-Next(8.4.0):
6.openEuler-24.03-LTS-SP1(8.4.0):
7.openEuler-24.03-LTS-SP3(8.4.0):
8.openEuler-24.03-LTS-SP4(8.4.0):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：

分支状态	原因说明	使用场景
受影响	正常修复	受影响且需要修复（包含升级版本修复）的漏洞；受影响且已经修复的漏洞（历史修复PR也需要关联issue）；若因特殊原因无法修复，应修改原因说明为【不修复-特殊原因】，并在安委会备案相关情况。
受影响	暂不修复-漏洞仍在分析中	已关注到相关漏洞，正在处理，未明确漏洞影响和修复方案。
受影响	暂不修复-暂无解决方案或补丁	当前没有可用的修复或补救措施。【影响性分析】中应包含有关为什么没有修复或补救措施的详细说明、上游相关PR等。
受影响	不修复-超出修复范围	没有漏洞的修复计划。当版本停维、软件包宣布生命周期终止或弃用使用。
受影响	不修复-特殊原因导致不再修复	如存在其他特殊情况不修复相关漏洞，或评估后无法升级修复，应在openEuler社区安全委员会例会进行说明备案。【影响性分析】中应包含不发布修复的详细说明、特殊情况还应有安委会会议纪要。
不受影响	不受影响-组件不存在	软件不受影响，因为易受攻击的组件不在产品中。
不受影响	不受影响-已有内置的内联控制或缓解措施	内置的内联控制或缓解措施可防止攻击者利用漏洞
不受影响	不受影响-漏洞代码不能被攻击者触发	易受攻击的组件存在，并且该组件包含易受攻击的代码。但是，易受攻击的代码的使用方式使得攻击者无法进行任何预期的攻击。
不受影响	不受影响-漏洞代码不在执行路径	易受影响的代码在执行过程中不可访问，包括产品的非预期状态。产品不使用也不执行的组件。
不受影响	不受影响-漏洞代码不存在	产品不受影响，因为漏洞背后的代码在产品中不存在。与component_not_present不同的是，有问题的组件存在，但由于某种原因（例如安全的编译器选项）使漏洞的特定代码不存在于组件中。

issue处理具体操作请参考:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://docs.atomgit.com/docs/help/home/org_project/pullrequests/pr-related-issue

openeuler-ci-bot成员

4月29日添加了label：sig/Networking

openeuler-ci-bot成员

4月29日评论：

Welcome To openEuler Community

Hey @openLiBingCI , thanks for your contribution to the community.

Bot Usage Manual

I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands.

Contact Guide

If you have any questions, please contact the SIG: Networking ,
and any of the maintainers: @Apricity_HW, @MrRlu, @robert-xingwang, @sunsuwan ,
and any of the committers: @jiangheng12138, @zhongxuan2 .

openeuler-ci-bot成员

4月29日评论：

参考网址	关联pr	状态	补丁链接
https://www.opencve.io/cve/CVE-2026-5545
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-5545
https://security-tracker.debian.org/tracker/CVE-2026-5545	None	None	https://github.com/curl/curl/commit/33e43985b8f3b9e6669 https://github.com/curl/curl/commit/e56ae1426c
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-5545
https://nvd.nist.gov/vuln/detail/CVE-2026-5545
https://ubuntu.com/security/CVE-2026-5545

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

openeuler-ci-bot成员

4月29日修改了issue 的描述

此处折叠了18条事件消息查看更多

S sherlock2010

5月19日关联了pull request：fix CVE-2026-4873 CVE-2026-5545 CVE-2026-5773 CVE-2026-6253 CVE-2026-6276 CVE-2026-6429 CVE-2026-7168

sherlock2010

5月19日评论：

影响性分析说明：libcurl might in some circumstances reuse the wrong connection when asked todo an authenticated HTTP(S) request after a Negotiate-authenticated one, whenboth use the same host.libcurl features a pool of recent connections so that subsequent requests canreuse an existing connection to avoid overhead.When reusing a connection a range of criteria must be met. Due to a logicalerror in the code, a request that was issued by an application couldwrongfully reuse an existing connection to the same server that wasauthenticated using different credentials.An application that first uses Negotiate authentication to a server withuser1:password1 and then does another operation to the same server askingfor any authentication method but for user2:password2 (while the previousconnection is still alive) - the second request gets confused and wronglyreuses the same connection and sends the new request over that connectionthinking it uses a mix of user1 s and user2 s credentials when it is in factstill using the connection authenticated for user1...

openEuler评分：6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

受影响版本排查(受影响/不受影响)：
1.master(8.20.0):不受影响
2.openEuler-20.03-LTS-SP4(7.71.1):受影响
3.openEuler-22.03-LTS-SP4(7.79.1):受影响
4.openEuler-24.03-LTS(8.4.0):受影响
5.openEuler-24.03-LTS-Next(8.4.0):受影响
6.openEuler-24.03-LTS-SP1(8.4.0):受影响
7.openEuler-24.03-LTS-SP3(8.4.0):受影响
8.openEuler-24.03-LTS-SP4(8.4.0):受影响

openeuler-ci-bot成员

5月19日修改了issue 的描述

openeuler-ci-bot成员

5月19日评论：

@zhongxuan2 经过 cve-manager 解析, 已分析的内容如下表所示:

状态	分析项目	内容
已分析	1.影响性分析说明	libcurl might in some circumstances reuse the wrong connection when asked todo an authenticated HTTP(S) request after a Negotiate-authenticated one, whenboth use the same host.libcurl features a pool of recent connections so that subsequent requests canreuse an existing connection to avoid overhead.When reusing a connection a range of criteria must be met. Due to a logicalerror in the code, a request that was issued by an application couldwrongfully reuse an existing connection to the same server that wasauthenticated using different credentials.An application that first uses Negotiate authentication to a server withuser1:password1 and then does another operation to the same server askingfor any authentication method but for user2:password2 (while the previousconnection is still alive) - the second request gets confused and wronglyreuses the same connection and sends the new request over that connectionthinking it uses a mix of user1 s and user2 s credentials when it is in factstill using the connection authenticated for user1...
已分析	2.openEulerScore	6.5
已分析	3.openEulerVector	AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
已分析	4.受影响版本排查	master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响
已分析	5.是否涉及abi变化	master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否
已分析	6.原因说明	master:不受影响-已有内置的内联控制或缓解措施,openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-Next:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

openeuler-ci-bot成员

5月19日评论：

经过cve-manager解析，部分分支PR未合入，如红色字体所示：

原因说明：
1.master:不受影响-已有内置的内联控制或缓解措施
2.openEuler-20.03-LTS-SP4:正常修复(PR未合入)
3.openEuler-22.03-LTS-SP4:正常修复(PR未合入)
4.openEuler-24.03-LTS:正常修复
5.openEuler-24.03-LTS-Next:正常修复
6.openEuler-24.03-LTS-SP1:正常修复
7.openEuler-24.03-LTS-SP3:正常修复
8.openEuler-24.03-LTS-SP4:正常修复

openeuler-ci-bot成员

5月19日 issue状态由待办的改变为进行中

sherlock2010

5月19日评论：

/check-issue

openeuler-ci-bot成员

5月19日评论：

@zhongxuan2 经过 cve-manager 解析, 已分析的内容如下表所示:

状态	分析项目	内容
已分析	1.影响性分析说明	libcurl might in some circumstances reuse the wrong connection when asked todo an authenticated HTTP(S) request after a Negotiate-authenticated one, whenboth use the same host.libcurl features a pool of recent connections so that subsequent requests canreuse an existing connection to avoid overhead.When reusing a connection a range of criteria must be met. Due to a logicalerror in the code, a request that was issued by an application couldwrongfully reuse an existing connection to the same server that wasauthenticated using different credentials.An application that first uses Negotiate authentication to a server withuser1:password1 and then does another operation to the same server askingfor any authentication method but for user2:password2 (while the previousconnection is still alive) - the second request gets confused and wronglyreuses the same connection and sends the new request over that connectionthinking it uses a mix of user1 s and user2 s credentials when it is in factstill using the connection authenticated for user1...
已分析	2.openEulerScore	6.5
已分析	3.openEulerVector	AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
已分析	4.受影响版本排查	master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响
已分析	5.是否涉及abi变化	master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否
已分析	6.原因说明	master:不受影响-已有内置的内联控制或缓解措施,openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-Next:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

openeuler-ci-bot成员

5月19日 issue状态由进行中改变为已完成

openeuler-ci-bot成员

5月19日关闭了 issue

openeuler-ci-bot成员

5月19日删除了label：CVE/UNFIXED

openeuler-ci-bot成员

5月19日添加了label：CVE/FIXED