openeuler-ci-botissue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(0.6.4):
2.openEuler-20.03-LTS-SP4(0.4.8):
3.openEuler-22.03-LTS-SP4(0.4.8):
4.openEuler-24.03-LTS-Next(0.5.1):
5.openEuler-24.03-LTS-SP1(0.5.1):
6.openEuler-24.03-LTS-SP3(0.5.1):
7.openEuler-24.03-LTS-SP4(0.5.1):
修复是否涉及abi变化(是/否)：
1.master(0.6.4):
2.openEuler-20.03-LTS-SP4(0.4.8):
3.openEuler-22.03-LTS-SP4(0.4.8):
4.openEuler-24.03-LTS-Next(0.5.1):
5.openEuler-24.03-LTS-SP1(0.5.1):
6.openEuler-24.03-LTS-SP3(0.5.1):
7.openEuler-24.03-LTS-SP4(0.5.1):
原因说明：
1.master(0.6.4):
2.openEuler-20.03-LTS-SP4(0.4.8):
3.openEuler-22.03-LTS-SP4(0.4.8):
4.openEuler-24.03-LTS-Next(0.5.1):
5.openEuler-24.03-LTS-SP1(0.5.1):
6.openEuler-24.03-LTS-SP3(0.5.1):
7.openEuler-24.03-LTS-SP4(0.5.1):
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：
分支状态 |
原因说明 | 使用场景 |
|---|---|---|
| 受影响 | 正常修复 | 受影响且需要修复（包含升级版本修复）的漏洞； 受影响且已经修复的漏洞（历史修复PR也需要关联issue）； 若因特殊原因无法修复，应修改原因说明为【不修复-特殊原因】，并在安委会备案相关情况。 |
| 受影响 | 暂不修复-漏洞仍在分析中 | 已关注到相关漏洞，正在处理，未明确漏洞影响和修复方案。 |
| 受影响 | 暂不修复-暂无解决方案或补丁 | 当前没有可用的修复或补救措施。【影响性分析】中应包含有关为什么没有修复或补救措施的详细说明、上游相关PR等。 |
| 受影响 | 不修复-超出修复范围 | 没有漏洞的修复计划。当版本停维、软件包宣布生命周期终止或弃用使用。 |
| 受影响 | 不修复-特殊原因导致不再修复 | 如存在其他特殊情况不修复相关漏洞，或评估后无法升级修复，应在openEuler社区安全委员会例会进行说明备案。 【影响性分析】中应包含不发布修复的详细说明、特殊情况还应有安委会会议纪要。 |
| 受影响 | 应源码修复-openEuler社区发布软件包不受影响 | 源码存在漏洞，但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
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: Programming-language ,
and any of the maintainers: @Charlie_li1, @lostway1 ,
and any of the committers: @lyn1001, @randy1568, @wk333 .
| 参考网址 | 关联pr | 状态 | 补丁链接 |
|---|---|---|---|
| https://www.opencve.io/cve/CVE-2026-119195 | None | None | https://github.com/pyasn1/pyasn1/commit/4ce00797c594b59c1fd6b86d9ebc3ba87b7ec9f9 |
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-119195 | |||
| https://security-tracker.debian.org/tracker/CVE-2026-119195 | None | None | https://github.com/pyasn1/pyasn1/commit/4ce00797c594b59c1fd6b86d9ebc3ba87b7ec9f9 |
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-119195 | |||
| https://nvd.nist.gov/vuln/detail/CVE-2026-119195 | |||
| https://ubuntu.com/security/CVE-2026-119195 | None | None | https://discourse.ubuntu.com/c/project https://github.com/pyasn1/pyasn1/commit/4ce00797c594b59c1fd6b86d9ebc3ba87b7ec9f9 |
说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用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同步成功, 稍后请重新加载页面.
任务已识别：根据事实清单为 issue #20（python-pyasn1，master 分支）生成 CVE-2026-119195 的评论。事实已与流水线状态文件核对一致（Step 4 判定 APPLICABLE、补丁 applied_clean、Step 5 rpmbuild -bp 失败、无 PR）。以下为评论内容：
【任务 #20 · master】CVE-2026-119195
1. 是否受影响
结论：受影响。
原因：CVE-2026-119195 的自有补丁经 Step 4 源码影响性分析判为 APPLICABLE（git apply --check succeeded，补丁可干净应用），表明漏洞代码存在于本版本源码中，需要修复。
分支状态：
- master（0.6.4）：受影响
2. 是否有修复补丁
已找到上游社区修复补丁：
https://github.com/pyasn1/pyasn1/commit/4ce00797c594b59c1fd6b86d9ebc3ba87b7ec9f9.patch
3. 补丁适配情况
本 CVE 无需适配。补丁 backport-CVE-2026-119195.patch 对 0.6.4 源码经 git apply --check 验证可干净应用（状态 applied_clean，置信度 high），无任何冲突项，核心修复逻辑与上游补丁保持一致，无需调整行号、上下文或 API。无前置补丁。rpmbuild -bp 构建级验证未通过，详见第 5 部分。
4. 是否提交 PR
未提交 PR。
5. 流水线失败原因
流水线在 Step 5 补丁适配 失败，最后检查点为 Step 3: 源码展开 完成。补丁以 Patch#6000 写入 spec 后，rpmbuild -bp（%prep 阶段）验证失败（exit 1），自动回退重新适配 3 次仍失败，超过最大重试次数，Step 6 及后续步骤未能执行。
6. issue 模板字段块
──────── 复制以下内容回填 issue ────────
受影响版本排查(受影响/不受影响)：
1.master(0.6.4): 受影响
ABI 变化：否
原因说明：
1.正常修复
────────────────────────────────────────
影响性分析说明：
pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed string and indefinite-length ANY decoding repeatedly concatenates each fragment onto a growing bytes value. Attacker-controlled BER or CER data can use many constructed OCTET STRING or character-string fragments. DER rejects constructed OCTET STRING without a schema, but accepts its definite-length form when asn1Spec selects univ.OctetString; it also accepts constructed character strings such as UTF8String without a schema, even though those encodings are not valid DER. The separate indefinite-length ANY path is reachable in BER and CER when asn1Spec selects univ.Any; DER rejects indefinite lengths. OctetStringPayloadDecoder uses growing header concatenation and AnyPayloadDecoder.indefLenValueDecoder uses growing chunk concatenation, repeatedly copying an increasing prefix and causing quadratic work. A sufficiently fragmented value can occupy decoding workers and cause CPU exhaustion without confidentiality or integrity impact. This issue is fixed in version 0.6.5.
openEuler评分：
7.5
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.master(0.6.4):受影响
2.openEuler-20.03-LTS-SP4(0.4.8):受影响
3.openEuler-22.03-LTS-SP4(0.4.8):受影响
4.openEuler-24.03-LTS-Next(0.5.1):受影响
5.openEuler-24.03-LTS-SP1(0.5.1):受影响
6.openEuler-24.03-LTS-SP3(0.5.1):受影响
7.openEuler-24.03-LTS-SP4(0.5.1):受影响
修复是否涉及abi变化(是/否)：
1.master(0.6.4):否
2.openEuler-20.03-LTS-SP4(0.4.8):否
3.openEuler-22.03-LTS-SP4(0.4.8):否
4.openEuler-24.03-LTS-Next(0.5.1):否
5.openEuler-24.03-LTS-SP1(0.5.1):否
6.openEuler-24.03-LTS-SP3(0.5.1):否
7.openEuler-24.03-LTS-SP4(0.5.1):否
原因说明：
1.master(0.6.4):正常修复
2.openEuler-20.03-LTS-SP4(0.4.8):不修复-超出修复范围
3.openEuler-22.03-LTS-SP4(0.4.8):正常修复
4.openEuler-24.03-LTS-Next(0.5.1):正常修复
5.openEuler-24.03-LTS-SP1(0.5.1):正常修复
6.openEuler-24.03-LTS-SP3(0.5.1):正常修复
7.openEuler-24.03-LTS-SP4(0.5.1):正常修复
@fundawang 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed string and indefinite-length ANY decoding repeatedly concatenates each fragment onto a growing bytes value. Attacker-controlled BER or CER data can use many constructed OCTET STRING or character-string fragments. DER rejects constructed OCTET STRING without a schema, but accepts its definite-length form when asn1Spec selects univ.OctetString; it also accepts constructed character strings such as UTF8String without a schema, even though those encodings are not valid DER. The separate indefinite-length ANY path is reachable in BER and CER when asn1Spec selects univ.Any; DER rejects indefinite lengths. OctetStringPayloadDecoder uses growing header concatenation and AnyPayloadDecoder.indefLenValueDecoder uses growing chunk concatenation, repeatedly copying an increasing prefix and causing quadratic work. A sufficiently fragmented value can occupy decoding workers and cause CPU exhaustion without confidentiality or integrity impact. This issue is fixed in version 0.6.5. |
| 已分析 | 2.openEulerScore | 7.5 |
| 已分析 | 3.openEulerVector | AV:N/AC:L/PR:N/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-manager解析，部分分支PR未合入，如红色字体所示：
原因说明：
1.master:正常修复(PR未合入)
2.openEuler-20.03-LTS-SP4:正常修复(PR未合入)
3.openEuler-22.03-LTS-SP4:正常修复(PR未合入)
4.openEuler-24.03-LTS-Next:正常修复(PR未合入)
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复(PR未合入)
@fundawang 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed string and indefinite-length ANY decoding repeatedly concatenates each fragment onto a growing bytes value. Attacker-controlled BER or CER data can use many constructed OCTET STRING or character-string fragments. DER rejects constructed OCTET STRING without a schema, but accepts its definite-length form when asn1Spec selects univ.OctetString; it also accepts constructed character strings such as UTF8String without a schema, even though those encodings are not valid DER. The separate indefinite-length ANY path is reachable in BER and CER when asn1Spec selects univ.Any; DER rejects indefinite lengths. OctetStringPayloadDecoder uses growing header concatenation and AnyPayloadDecoder.indefLenValueDecoder uses growing chunk concatenation, repeatedly copying an increasing prefix and causing quadratic work. A sufficiently fragmented value can occupy decoding workers and cause CPU exhaustion without confidentiality or integrity impact. This issue is fixed in version 0.6.5. |
| 已分析 | 2.openEulerScore | 7.5 |
| 已分析 | 3.openEulerVector | AV:N/AC:L/PR:N/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-manager解析，部分分支PR未合入，如红色字体所示：
原因说明：
1.master:正常修复(PR未合入)
2.openEuler-20.03-LTS-SP4:不修复-超出修复范围
3.openEuler-22.03-LTS-SP4:正常修复(PR未合入)
4.openEuler-24.03-LTS-Next:正常修复(PR未合入)
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复(PR未合入)
经过cve-manager解析，部分分支PR未合入，如红色字体所示：
原因说明：
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:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复
经过cve-manager解析，所有PR均已合入
一、漏洞信息
漏洞编号：CVE-2026-119195
漏洞归属组件：python-pyasn1
漏洞归属的版本：0.3.7,0.4.8,0.5.1,0.6.1,0.6.4
CVSS评分：
BaseScore：0.0 None
Vector：
漏洞简述：
pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed string and indefinite-length ANY decoding repeatedly concatenates each fragment onto a growing bytes value. Attacker-controlled BER or CER data can use many constructed OCTET STRING or character-string fragments. DER rejects constructed OCTET STRING without a schema, but accepts its definite-length form when asn1Spec selects univ.OctetString; it also accepts constructed character strings such as UTF8String without a schema, even though those encodings are not valid DER. The separate indefinite-length ANY path is reachable in BER and CER when asn1Spec selects univ.Any; DER rejects indefinite lengths. OctetStringPayloadDecoder uses growing header concatenation and AnyPayloadDecoder.indefLenValueDecoder uses growing chunk concatenation, repeatedly copying an increasing prefix and causing quadratic work. A sufficiently fragmented value can occupy decoding workers and cause CPU exhaustion without confidentiality or integrity impact. This issue is fixed in version 0.6.5.
漏洞公开时间：2026-10-30 04:17:30
漏洞创建时间：2026-10-31 23:49:09
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-119195
更多参考(点击展开)
无
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
其他
漏洞补丁信息：
详情(点击展开)
无
二、漏洞分析结构反馈
影响性分析说明：
pyasn1 is a generic ASN.1 library for Python. Prior to 0.6.5, constructed string and indefinite-length ANY decoding repeatedly concatenates each fragment onto a growing bytes value. Attacker-controlled BER or CER data can use many constructed OCTET STRING or character-string fragments. DER rejects constructed OCTET STRING without a schema, but accepts its definite-length form when asn1Spec selects univ.OctetString; it also accepts constructed character strings such as UTF8String without a schema, even though those encodings are not valid DER. The separate indefinite-length ANY path is reachable in BER and CER when asn1Spec selects univ.Any; DER rejects indefinite lengths. OctetStringPayloadDecoder uses growing header concatenation and AnyPayloadDecoder.indefLenValueDecoder uses growing chunk concatenation, repeatedly copying an increasing prefix and causing quadratic work. A sufficiently fragmented value can occupy decoding workers and cause CPU exhaustion without confidentiality or integrity impact. This issue is fixed in version 0.6.5.
openEuler评分：
7.5
Vector：CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响)：
1.master(0.6.4):受影响
2.openEuler-20.03-LTS-SP4(0.4.8):受影响
3.openEuler-22.03-LTS-SP4(0.4.8):受影响
4.openEuler-24.03-LTS-Next(0.5.1):受影响
5.openEuler-24.03-LTS-SP1(0.5.1):受影响
6.openEuler-24.03-LTS-SP3(0.5.1):受影响
7.openEuler-24.03-LTS-SP4(0.5.1):受影响
修复是否涉及abi变化(是/否)：
1.master(0.6.4):否
2.openEuler-20.03-LTS-SP4(0.4.8):否
3.openEuler-22.03-LTS-SP4(0.4.8):否
4.openEuler-24.03-LTS-Next(0.5.1):否
5.openEuler-24.03-LTS-SP1(0.5.1):否
6.openEuler-24.03-LTS-SP3(0.5.1):否
7.openEuler-24.03-LTS-SP4(0.5.1):否
原因说明：
1.master(0.6.4):正常修复
2.openEuler-20.03-LTS-SP4(0.4.8):不修复-超出修复范围
3.openEuler-22.03-LTS-SP4(0.4.8):正常修复
4.openEuler-24.03-LTS-Next(0.5.1):正常修复
5.openEuler-24.03-LTS-SP1(0.5.1):正常修复
6.openEuler-24.03-LTS-SP3(0.5.1):正常修复
7.openEuler-24.03-LTS-SP4(0.5.1):正常修复