@zhuchunyi ,@zhongjun2 ,@genedna ,@yikunkero ,@Zherphy ,@georgecao ,@TommyLike ,@imjoey
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.
影响性分析说明:
openEuler评分: (评分和向量)
受影响版本排查(受影响/不受影响):
1.master(3.7.0):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3:
4.openEuler-22.03-LTS-SP4(3.5.1):
5.openEuler-24.03-LTS(3.2.0):
6.openEuler-24.03-LTS-Next(3.6.1):
7.openEuler-24.03-LTS-SP1:
8.openEuler-24.03-LTS-SP2:
修复是否涉及abi变化(是/否)：
1.master(3.7.0):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3:
4.openEuler-22.03-LTS-SP4(3.5.1):
5.openEuler-24.03-LTS(3.2.0):
6.openEuler-24.03-LTS-Next(3.6.1):
7.openEuler-24.03-LTS-SP1:
8.openEuler-24.03-LTS-SP2:
原因说明：
1.master(3.7.0):
2.openEuler-20.03-LTS-SP4:
3.openEuler-22.03-LTS-SP3:
4.openEuler-22.03-LTS-SP4(3.5.1):
5.openEuler-24.03-LTS(3.2.0):
6.openEuler-24.03-LTS-Next(3.6.1):
7.openEuler-24.03-LTS-SP1:
8.openEuler-24.03-LTS-SP2:
原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：
| 分支状态 | 原因说明 |
|---|---|
| 受影响 | 正常修复 |
| 受影响 | 暂不修复-漏洞仍在分析中 |
| 受影响 | 暂不修复-暂无解决方案或补丁 |
| 受影响 | 暂不修复-待升级版本修复 |
| 受影响 | 不修复-超出修复范围 |
| 受影响 | 不修复-特殊原因导致不再修复 |
| 不受影响 | 不受影响-组件不存在 |
| 不受影响 | 不受影响-已有内置的内联控制或缓解措施 |
| 不受影响 | 不受影响-漏洞代码不能被攻击者触发 |
| 不受影响 | 不受影响-漏洞代码不在执行路径 |
| 不受影响 | 不受影响-漏洞代码不存在 |
issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142
Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Infrastructure, and any of the maintainers: @genedna , @yikunkero , @georgecao , @TommyLike , @imjoey , @zhuchunyi , @zhongjun2 , any of the committers: @Zherphy
| 参考网址 | 关联pr | 状态 | 补丁链接 |
|---|---|---|---|
| https://nvd.nist.gov/vuln/detail/CVE-2025-26625 | |||
| https://ubuntu.com/security/CVE-2025-26625 | None | None | https://discourse.ubuntu.com/c/project |
| https://www.opencve.io/cve/CVE-2025-26625 | |||
| https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2025-26625 | |||
| https://security-tracker.debian.org/tracker/CVE-2025-26625 | |||
| http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2025-26625 |
说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1
影响性分析说明：
When populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS.
openEuler评分：
8.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
受影响版本排查(受影响/不受影响)：
1.master(3.7.0):受影响
2.openEuler-20.03-LTS-SP4:不受影响
3.openEuler-22.03-LTS-SP3:不受影响
4.openEuler-22.03-LTS-SP4(3.5.1):受影响
5.openEuler-24.03-LTS(3.2.0):受影响
6.openEuler-24.03-LTS-Next(3.6.1):受影响
7.openEuler-24.03-LTS-SP1:不受影响
8.openEuler-24.03-LTS-SP2:不受影响
修复是否涉及abi变化(是/否)：
1.master(3.7.0):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4(3.5.1):否
5.openEuler-24.03-LTS(3.2.0):否
6.openEuler-24.03-LTS-Next(3.6.1):否
7.openEuler-24.03-LTS-SP1:否
8.openEuler-24.03-LTS-SP2:否
原因说明：
1.master(3.7.0):正常修复
2.openEuler-20.03-LTS-SP4:不受影响-组件不存在
3.openEuler-22.03-LTS-SP3:不受影响-组件不存在
4.openEuler-22.03-LTS-SP4(3.5.1):正常修复
5.openEuler-24.03-LTS(3.2.0):正常修复
6.openEuler-24.03-LTS-Next(3.6.1):正常修复
7.openEuler-24.03-LTS-SP1:不受影响-组件不存在
8.openEuler-24.03-LTS-SP2:不受影响-组件不存在
@Zherphy 经过 cve-manager 解析, 已分析的内容如下表所示:
| 状态 | 分析项目 | 内容 |
|---|---|---|
| 已分析 | 1.影响性分析说明 | When populating a Git repository's working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. |
| 已分析 | 2.openEulerScore | 8.8 |
| 已分析 | 3.openEulerVector | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| 已分析 | 4.受影响版本排查 | master:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:受影响,openEuler-20.03-LTS-SP4:不受影响,openEuler-22.03-LTS-SP3:不受影响,openEuler-24.03-LTS-SP1:不受影响,openEuler-24.03-LTS-SP2:不受影响 |
| 已分析 | 5.是否涉及abi变化 | master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP2:否 |
| 已分析 | 6.原因说明 | master:正常修复,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-Next:正常修复,openEuler-20.03-LTS-SP4:不受影响-组件不存在,openEuler-22.03-LTS-SP3:不受影响-组件不存在,openEuler-24.03-LTS-SP1:不受影响-组件不存在,openEuler-24.03-LTS-SP2:不受影响-组件不存在 |
请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.
一、漏洞信息
漏洞编号：CVE-2025-26625
漏洞归属组件：git-lfs
漏洞归属的版本：2.12.0,3.2.0,3.5.1,3.6.1,3.7.0,3.7.1
CVSS评分：
BaseScore：8.6 High
Vector：CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
漏洞简述：
Git LFS is a Git extension for versioning large files. In Git LFS versions 0.5.2 through 3.7.0, when populating a Git repository s working tree with the contents of Git LFS objects, certain Git LFS commands may write to files visible outside the current Git working tree if symbolic or hard links exist which collide with the paths of files tracked by Git LFS. The git lfs checkout and git lfs pull commands do not check for symbolic links before writing to files in the working tree, allowing an attacker to craft a repository containing symbolic or hard links that cause Git LFS to write to arbitrary file system locations accessible to the user running these commands. As well, when the git lfs checkout and git lfs pull commands are run in a bare repository, they could write to files visible outside the repository. The vulnerability is fixed in version 3.7.1. As a workaround, support for symlinks in Git may be disabled by setting the core.symlinks configuration option to false, after which further clones and fetches will not create symbolic links. However, any symbolic or hard links in existing repositories will still provide the opportunity for Git LFS to write to their targets.
漏洞公开时间：2025-10-18 00:15:37
漏洞创建时间：2025-10-17 14:01:19
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2025-26625
更多参考(点击展开)
漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息：
详情(点击展开)
二、漏洞分析结构反馈
影响性分析说明：
新版本的git-lfs中该漏洞已修复
openEuler评分：
8.6
Vector：CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
受影响版本排查(受影响/不受影响)：
1.master(3.7.1):不受影响
2.openEuler-22.03-LTS-SP4(3.5.1):不受影响
3.openEuler-24.03-LTS(3.2.0):不受影响
4.openEuler-24.03-LTS-Next(3.6.1):不受影响
5.openEuler-24.03-LTS-SP1(3.6.1):不受影响
6.openEuler-24.03-LTS-SP2(3.6.1):不受影响
7.openEuler-20.03-LTS-SP4:不受影响
8.openEuler-22.03-LTS-SP3:不受影响
9.openEuler-24.03-LTS-SP3(3.6.1):不受影响
10.openEuler-24.03-LTS-SP4(3.6.1):不受影响
修复是否涉及abi变化(是/否)：
1.master(3.7.1):否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4(3.5.1):否
5.openEuler-24.03-LTS(3.2.0):否
6.openEuler-24.03-LTS-Next(3.6.1):否
7.openEuler-24.03-LTS-SP1(3.6.1):否
8.openEuler-24.03-LTS-SP2(3.6.1):否
9.openEuler-24.03-LTS-SP3(3.6.1):否
10.openEuler-24.03-LTS-SP4(3.6.1):否
原因说明：
1.master(3.7.1):不受影响-组件不存在
2.openEuler-22.03-LTS-SP4(3.5.1):不受影响-组件不存在
3.openEuler-24.03-LTS(3.2.0):不受影响-组件不存在
4.openEuler-24.03-LTS-Next(3.6.1):不受影响-组件不存在
5.openEuler-24.03-LTS-SP1(3.6.1):不受影响-组件不存在
6.openEuler-24.03-LTS-SP2(3.6.1):不受影响-组件不存在
7.openEuler-20.03-LTS-SP4:不受影响-组件不存在
8.openEuler-22.03-LTS-SP3:不受影响-组件不存在
9.openEuler-24.03-LTS-SP3(3.6.1):不受影响-组件不存在
10.openEuler-24.03-LTS-SP4(3.6.1):不受影响-组件不存在