Welcome To openEuler Community
Hey @jade_t , 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: sig-CloudNative ,
and any of the maintainers: @duguhaotian, @gaodaweiky, @jimmieme, @lu-wei-army, @weibaohui, @wonleing, @yangzhao_kl, @zhaoyifan28, @zmr_2020 ,
and any of the committers: @Yekelu .
issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(1.6.22):
2.openEuler-20.03-LTS-SP4(1.2.0):
3.openEuler-22.03-LTS-SP4(1.2.0):
4.openEuler-24.03-LTS-Next(1.6.22):
5.openEuler-24.03-LTS-SP1(1.6.22):
6.openEuler-24.03-LTS-SP3(1.6.22):
7.openEuler-24.03-LTS-SP4(1.6.22):
修复是否涉及abi变化(是/否)：
1.master(1.6.22):
2.openEuler-20.03-LTS-SP4(1.2.0):
3.openEuler-22.03-LTS-SP4(1.2.0):
4.openEuler-24.03-LTS-Next(1.6.22):
5.openEuler-24.03-LTS-SP1(1.6.22):
6.openEuler-24.03-LTS-SP3(1.6.22):
7.openEuler-24.03-LTS-SP4(1.6.22):
原因说明：
1.master(1.6.22):
2.openEuler-20.03-LTS-SP4(1.2.0):
3.openEuler-22.03-LTS-SP4(1.2.0):
4.openEuler-24.03-LTS-Next(1.6.22):
5.openEuler-24.03-LTS-SP1(1.6.22):
6.openEuler-24.03-LTS-SP3(1.6.22):
7.openEuler-24.03-LTS-SP4(1.6.22):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如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
| 参考网址 | 关联pr | 状态 | 补丁链接 |
|---|---|---|---|
| https://www.opencve.io/cve/CVE-2026-35469 | |||
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-35469 | |||
| https://security-tracker.debian.org/tracker/CVE-2026-35469 | |||
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-35469 | |||
| https://nvd.nist.gov/vuln/detail/CVE-2026-35469 | |||
| https://ubuntu.com/security/CVE-2026-35469 | None | None | https://discourse.ubuntu.com/c/project |
说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1
@jade_t CVE信息从NVD同步成功, 稍后请重新加载页面.
经过cve-manager解析，部分字段填写错误，如红色字体所示：
影响性分析说明:
(请填写此字段)
openEuler评分: (评分和向量)
(请填写此字段)
受影响版本排查(受影响/不受影响):
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP4:(请填写此字段)
4.openEuler-24.03-LTS-Next:(请填写此字段)
5.openEuler-24.03-LTS-SP1:(请填写此字段)
6.openEuler-24.03-LTS-SP3:(请填写此字段)
7.openEuler-24.03-LTS-SP4:(请填写此字段)
修复是否涉及abi变化(是/否)：
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP4:(请填写此字段)
4.openEuler-24.03-LTS-Next:(请填写此字段)
5.openEuler-24.03-LTS-SP1:(请填写此字段)
6.openEuler-24.03-LTS-SP3:(请填写此字段)
7.openEuler-24.03-LTS-SP4:(请填写此字段)
原因说明：
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP4:(请填写此字段)
4.openEuler-24.03-LTS-Next:(请填写此字段)
5.openEuler-24.03-LTS-SP1:(请填写此字段)
6.openEuler-24.03-LTS-SP3:(请填写此字段)
7.openEuler-24.03-LTS-SP4:(请填写此字段)
经过cve-manager解析，部分字段填写错误，如红色字体所示：
影响性分析说明:
(请填写此字段)
openEuler评分: (评分和向量)
(请填写此字段)
受影响版本排查(受影响/不受影响):
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP4:(请填写此字段)
4.openEuler-24.03-LTS-Next:(请填写此字段)
5.openEuler-24.03-LTS-SP1:(请填写此字段)
6.openEuler-24.03-LTS-SP3:(请填写此字段)
7.openEuler-24.03-LTS-SP4:(请填写此字段)
修复是否涉及abi变化(是/否)：
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP4:(请填写此字段)
4.openEuler-24.03-LTS-Next:(请填写此字段)
5.openEuler-24.03-LTS-SP1:(请填写此字段)
6.openEuler-24.03-LTS-SP3:(请填写此字段)
7.openEuler-24.03-LTS-SP4:(请填写此字段)
原因说明：
1.master:(请填写此字段)
2.openEuler-20.03-LTS-SP4:(请填写此字段)
3.openEuler-22.03-LTS-SP4:(请填写此字段)
4.openEuler-24.03-LTS-Next:(请填写此字段)
5.openEuler-24.03-LTS-SP1:(请填写此字段)
6.openEuler-24.03-LTS-SP3:(请填写此字段)
7.openEuler-24.03-LTS-SP4:(请填写此字段)
影响性分析说明:
spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.
openEuler评分: (评分和向量)
6.5
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响):
1.master(1.6.22):受影响
2.openEuler-20.03-LTS-SP4(1.2.0):受影响
3.openEuler-22.03-LTS-SP4(1.2.0):受影响
4.openEuler-24.03-LTS-Next(1.6.22):受影响
5.openEuler-24.03-LTS-SP1(1.6.22):受影响
6.openEuler-24.03-LTS-SP3(1.6.22):受影响
7.openEuler-24.03-LTS-SP4(1.6.22):受影响
修复是否涉及abi变化(是/否)：
1.master(1.6.22):否
2.openEuler-20.03-LTS-SP4(1.2.0):否
3.openEuler-22.03-LTS-SP4(1.2.0):否
4.openEuler-24.03-LTS-Next(1.6.22):否
5.openEuler-24.03-LTS-SP1(1.6.22):否
6.openEuler-24.03-LTS-SP3(1.6.22):否
7.openEuler-24.03-LTS-SP4(1.6.22):否
原因说明：
1.master(1.6.22):正常修复
2.openEuler-20.03-LTS-SP4(1.2.0):正常修复
3.openEuler-22.03-LTS-SP4(1.2.0):正常修复
4.openEuler-24.03-LTS-Next(1.6.22):正常修复
5.openEuler-24.03-LTS-SP1(1.6.22):正常修复
6.openEuler-24.03-LTS-SP3(1.6.22):正常修复
7.openEuler-24.03-LTS-SP4(1.6.22):正常修复
@Yekelu 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1. |
| 已分析 | 2.openEulerScore | 6.5 |
| 已分析 | 3.openEulerVector | AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| 已分析 | 4.受影响版本排查 | master:受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,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-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-Next:正常修复,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
一、漏洞信息
漏洞编号：CVE-2026-35469
漏洞归属组件：containerd
漏洞归属的版本：1.6.20
CVSS评分：
BaseScore：N/A None
Vector：
漏洞简述：
spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.
漏洞公开时间：2026-04-17 06:16
漏洞创建时间：2026-08-12 16:51:48
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-35469
更多参考(点击展开)
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息：
详情(点击展开)
二、漏洞分析结构反馈
影响性分析说明：
spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.
openEuler评分：
6.5
Vector：CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.master(1.6.22):受影响
2.openEuler-20.03-LTS-SP4(1.2.0):受影响
3.openEuler-22.03-LTS-SP4(1.2.0):受影响
4.openEuler-24.03-LTS-Next(1.6.22):受影响
5.openEuler-24.03-LTS-SP1(1.6.22):受影响
6.openEuler-24.03-LTS-SP3(1.6.22):受影响
7.openEuler-24.03-LTS-SP4(1.6.22):受影响
修复是否涉及abi变化(是/否)：
1.master(1.6.22):否
2.openEuler-20.03-LTS-SP4(1.2.0):否
3.openEuler-22.03-LTS-SP4(1.2.0):否
4.openEuler-24.03-LTS-Next(1.6.22):否
5.openEuler-24.03-LTS-SP1(1.6.22):否
6.openEuler-24.03-LTS-SP3(1.6.22):否
7.openEuler-24.03-LTS-SP4(1.6.22):否
原因说明：
1.master(1.6.22):正常修复
2.openEuler-20.03-LTS-SP4(1.2.0):正常修复
3.openEuler-22.03-LTS-SP4(1.2.0):正常修复
4.openEuler-24.03-LTS-Next(1.6.22):正常修复
5.openEuler-24.03-LTS-SP1(1.6.22):正常修复
6.openEuler-24.03-LTS-SP3(1.6.22):正常修复
7.openEuler-24.03-LTS-SP4(1.6.22):正常修复