Welcome To openEuler Community
Hey @fundawang , 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. You can self-configure the PR merge rules for this repository. For more details, please refer to Here.
Contact Guide
If you have any questions, please contact the SIG: sig-security-facility ,
and any of the maintainers: @mailofzxf, @robertosassu, @zhujianwei001 ,
and any of the committers: @gcw_n2PeTU3z, @zcfsite .
issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(3.5.8):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):
修复是否涉及abi变化(是/否)：
1.master(3.5.8):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):
原因说明：
1.master(3.5.8):
2.openEuler-20.03-LTS-SP4(1.1.1f):
3.openEuler-22.03-LTS-SP4(1.1.1wa):
4.openEuler-24.03-LTS-Next(3.5.6):
5.openEuler-24.03-LTS-SP1(3.0.12):
6.openEuler-24.03-LTS-SP3(3.0.12):
7.openEuler-24.03-LTS-SP4(3.5.6):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如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-75804 | |||
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-75804 | |||
| https://security-tracker.debian.org/tracker/CVE-2026-75804 | |||
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-75804 | |||
| https://nvd.nist.gov/vuln/detail/CVE-2026-75804 | |||
| https://ubuntu.com/security/CVE-2026-75804 | 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
@fundawang CVE信息从NVD同步失败, 请稍后重试, 或者数据源不存在.
/branches openEuler-20.03-LTS-SP4 openEuler-22.03-LTS-SP4 openEuler-24.03-LTS-SP1 openEuler-24.03-LTS-SP3 /name hugel /email 2712504175@qq.com
【任务 #292 · openEuler-24.03-LTS-SP3】CVE-2026-75804
1. 是否受影响
结论：不受影响。
CVE-2026-75804 的自有补丁经 Step 4 源码影响性分析判为 NOT_APPLICABLE，漏洞代码不存在于本版本源码中，无需修复。
各分支状态：
- openEuler-24.03-LTS-SP3（版本 3.0.12）：不受影响（漏洞代码不存在，补丁 NOT_APPLICABLE）
2. 是否有修复补丁
已找到上游社区修复补丁：
3. 补丁适配情况
无适配需求。由于本版本源码中不存在漏洞代码，修复补丁无需适配到 openEuler-24.03-LTS-SP3 分支。
4. 是否提交 PR
无 PR。该 CVE 不影响本分支，无需提交修复 PR。
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-24.03-LTS-SP3(3.0.12): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
【任务 #292 · openEuler-20.03-LTS-SP4】CVE-2026-75804
1. 是否受影响
结论：不受影响。
CVE-2026-75804 的自有补丁经 Step 4 源码影响性分析判为 NOT_APPLICABLE，漏洞代码不存在于本版本源码中，因此该分支无需修复。
各分支状态：
- openEuler-20.03-LTS-SP4（1.1.1f）：不受影响（漏洞代码不存在，补丁 NOT_APPLICABLE）
2. 是否有修复补丁
上游社区已有修复补丁：https://github.com/openssl/openssl/commit/f9eaecf5bdd6692da052bc65b0332af2a938ac03.patch
3. 补丁适配情况
无适配。该补丁经源码影响性分析判定为 NOT_APPLICABLE，漏洞代码在本分支源码中不存在，无需进行任何适配或应用。
4. 是否提交 PR
无 PR。由于本分支不受影响，未发起修复 PR。
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-20.03-LTS-SP4(1.1.1f): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
【任务 #292 · openEuler-24.03-LTS-SP1】CVE-2026-75804
1. 是否受影响
结论：不受影响。
经 Step 4 源码影响性分析，该 CVE 的自有补丁判为 NOT_APPLICABLE，漏洞代码不存在于本版本源码中，无需修复。
分支状态：
- openEuler-24.03-LTS-SP1（3.0.12）：不受影响（漏洞代码不存在，补丁 NOT_APPLICABLE），无 ABI 变化。
2. 是否有修复补丁
有上游社区修复补丁：
3. 补丁适配情况
无适配。由于漏洞代码不存在于 openEuler-24.03-LTS-SP1 的 openssl 3.0.12 源码中，该补丁无需适配，也未进行适配。
4. 是否提交 PR
无 PR。
5. 流水线失败原因
（本次流水线无失败记录，跳过。）
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-24.03-LTS-SP1(3.0.12): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
【任务 #292 · openEuler-22.03-LTS-SP4】CVE-2026-75804
1. 是否受影响：不受影响
CVE-2026-75804 的自有补丁经 Step 4 源码影响性分析判定为 NOT_APPLICABLE，漏洞相关代码不存在于本版本源码中，因此本分支不受影响，无需修复。
分支状态：
- openEuler-22.03-LTS-SP4（1.1.1wa）：不受影响（漏洞代码不存在，补丁 NOT_APPLICABLE）
2. 是否有修复补丁：有
上游社区修复补丁：
https://github.com/openssl/openssl/commit/f9eaecf5bdd6692da052bc65b0332af2a938ac03.patch
3. 补丁适配情况：无适配
本分支源码中不存在漏洞代码，该补丁经源码影响性分析即为不适用（NOT_APPLICABLE），无需进行任何适配，也无前置补丁。
4. 是否提交 PR：无
本分支不受影响，无需修复，故未提交修复 PR。
如需回填 issue 模板，可复制以下内容：
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.openEuler-22.03-LTS-SP4(1.1.1wa): 不受影响
ABI 变化：否
原因说明：
1.不受影响-漏洞代码不存在
────────────────────────────────────────
影响性分析说明：Issue summary: OpenSSL QUIC stack does not enforce connectionlevel flow control for streams. Remote peers may send more bytesas long as they fit within the stream flow control limits.Impact summary: A malicious remote peer may exploit the lack of connectionflow control for streams to make the QUIC stack receive ~100MB of memoryinstead of 768 KiB (default flow control window size).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: The local QUIC stack advertises two flow control limitsto its remote peer: stream flow control limit and connection flowcontrol limit. The remote peer must follow both limits when transmittingstream data.Whenever the local QUIC stack receives a stream frame, it validatesthat the size of the received stream frame stays within flow control limits.If either limit is exceeded (stream level or connection level), thenthe QUIC stack must close the connection with a flow control error.The vulnerable OpenSSL QUIC stack enforces the stream-level but notthe connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data).By meeting the conditions above, the remote peer may make the local stackallocate 2 x MAX_STREAMS x (stream flow control limit) bytesof memory. MAX_STREAMS defaults to 100, and the limit applies to bothbidirectional and unidirectional streams, making it 200 in total. The defaultflow control window for a stream is 512kB. The remote peer mayforce the vulnerable QUIC stack to allocate 100MB of heap per connection.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary.
openEuler评分：
5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
受影响版本排查(受影响/不受影响)：
1.master(3.5.8):受影响
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响
4.openEuler-24.03-LTS-Next(3.5.6):受影响
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响
7.openEuler-24.03-LTS-SP4(3.5.6):受影响
修复是否涉及abi变化(是/否)：
1.master(3.5.8):否
2.openEuler-20.03-LTS-SP4(1.1.1f):否
3.openEuler-22.03-LTS-SP4(1.1.1wa):否
4.openEuler-24.03-LTS-Next(3.5.6):否
5.openEuler-24.03-LTS-SP1(3.0.12):否
6.openEuler-24.03-LTS-SP3(3.0.12):否
7.openEuler-24.03-LTS-SP4(3.5.6):否
原因说明：
1.master(3.5.8):正常修复
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响-漏洞代码不存在
4.openEuler-24.03-LTS-Next(3.5.6):正常修复
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP4(3.5.6):正常修复
@robertosassu 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | Issue summary: OpenSSL QUIC stack does not enforce connectionlevel flow control for streams. Remote peers may send more bytesas long as they fit within the stream flow control limits.Impact summary: A malicious remote peer may exploit the lack of connectionflow control for streams to make the QUIC stack receive ~100MB of memoryinstead of 768 KiB (default flow control window size).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: The local QUIC stack advertises two flow control limitsto its remote peer: stream flow control limit and connection flowcontrol limit. The remote peer must follow both limits when transmittingstream data.Whenever the local QUIC stack receives a stream frame, it validatesthat the size of the received stream frame stays within flow control limits.If either limit is exceeded (stream level or connection level), thenthe QUIC stack must close the connection with a flow control error.The vulnerable OpenSSL QUIC stack enforces the stream-level but notthe connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data).By meeting the conditions above, the remote peer may make the local stackallocate 2 x MAX_STREAMS x (stream flow control limit) bytesof memory. MAX_STREAMS defaults to 100, and the limit applies to bothbidirectional and unidirectional streams, making it 200 in total. The defaultflow control window for a stream is 512kB. The remote peer mayforce the vulnerable QUIC stack to allocate 100MB of heap per connection.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary. |
| 已分析 | 2.openEulerScore | 5.3 |
| 已分析 | 3.openEulerVector | AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| 已分析 | 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-manager解析，(所有PR均已合入)
经过cve-manager解析，(所有PR均已合入)
一、漏洞信息
漏洞编号：CVE-2026-75804
漏洞归属组件：openssl
漏洞归属的版本：3.0.12
CVSS评分：
BaseScore：5.3 Medium
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
漏洞简述：
Issue summary: OpenSSL QUIC stack does not enforce connectionlevel flow control for streams. Remote peers may send more bytesas long as they fit within the stream flow control limits.Impact summary: A malicious remote peer may exploit the lack of connectionflow control for streams to make the QUIC stack receive ~100MB of memoryinstead of 768 KiB (default flow control window size).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: The local QUIC stack advertises two flow control limitsto its remote peer: stream flow control limit and connection flowcontrol limit. The remote peer must follow both limits when transmittingstream data.Whenever the local QUIC stack receives a stream frame, it validatesthat the size of the received stream frame stays within flow control limits.If either limit is exceeded (stream level or connection level), thenthe QUIC stack must close the connection with a flow control error.The vulnerable OpenSSL QUIC stack enforces the stream-level but notthe connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data).By meeting the conditions above, the remote peer may make the local stackallocate 2 x MAX_STREAMS x (stream flow control limit) bytesof memory. MAX_STREAMS defaults to 100, and the limit applies to bothbidirectional and unidirectional streams, making it 200 in total. The defaultflow control window for a stream is 512kB. The remote peer mayforce the vulnerable QUIC stack to allocate 100MB of heap per connection.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary.
漏洞公开时间：2026-09-30 00:17:10
漏洞创建时间：2026-09-29 23:27:25
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-75804
更多参考(点击展开)
无
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息：
详情(点击展开)
无
二、漏洞分析结构反馈
影响性分析说明：
Issue summary: OpenSSL QUIC stack does not enforce connectionlevel flow control for streams. Remote peers may send more bytesas long as they fit within the stream flow control limits.Impact summary: A malicious remote peer may exploit the lack of connectionflow control for streams to make the QUIC stack receive ~100MB of memoryinstead of 768 KiB (default flow control window size).CWE: CWE-770: Allocation of Resources Without Limits or ThrottlingDescription: The local QUIC stack advertises two flow control limitsto its remote peer: stream flow control limit and connection flowcontrol limit. The remote peer must follow both limits when transmittingstream data.Whenever the local QUIC stack receives a stream frame, it validatesthat the size of the received stream frame stays within flow control limits.If either limit is exceeded (stream level or connection level), thenthe QUIC stack must close the connection with a flow control error.The vulnerable OpenSSL QUIC stack enforces the stream-level but notthe connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data).By meeting the conditions above, the remote peer may make the local stackallocate 2 x MAX_STREAMS x (stream flow control limit) bytesof memory. MAX_STREAMS defaults to 100, and the limit applies to bothbidirectional and unidirectional streams, making it 200 in total. The defaultflow control window for a stream is 512kB. The remote peer mayforce the vulnerable QUIC stack to allocate 100MB of heap per connection.FIPS impact: noThe FIPS module is not affected as the QUIC implementation is outside ofthe OpenSSL FIPS module boundary.
openEuler评分：
5.3
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
受影响版本排查(受影响/不受影响)：
1.master(3.5.9):受影响
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响
4.openEuler-24.03-LTS-Next(3.5.6):受影响
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响
7.openEuler-24.03-LTS-SP4(3.5.6):受影响
修复是否涉及abi变化(是/否)：
1.master(3.5.9):否
2.openEuler-20.03-LTS-SP4(1.1.1f):否
3.openEuler-22.03-LTS-SP4(1.1.1wa):否
4.openEuler-24.03-LTS-Next(3.5.6):否
5.openEuler-24.03-LTS-SP1(3.0.12):否
6.openEuler-24.03-LTS-SP3(3.0.12):否
7.openEuler-24.03-LTS-SP4(3.5.6):否
原因说明：
1.master(3.5.9):正常修复
2.openEuler-20.03-LTS-SP4(1.1.1f):不受影响-漏洞代码不存在
3.openEuler-22.03-LTS-SP4(1.1.1wa):不受影响-漏洞代码不存在
4.openEuler-24.03-LTS-Next(3.5.6):正常修复
5.openEuler-24.03-LTS-SP1(3.0.12):不受影响-漏洞代码不存在
6.openEuler-24.03-LTS-SP3(3.0.12):不受影响-漏洞代码不存在
7.openEuler-24.03-LTS-SP4(3.5.6):正常修复