已开启
CVE-2026-15307 #123
openeuler-ci-bot创建于  25 天前
openeuler-ci-bot
openeuler-ci-bot成员
25 天前 创建

一、漏洞信息
漏洞编号:CVE-2026-15307
漏洞归属组件:python-django
漏洞归属的版本:1.11.13,1.11.18,2.2.27,2.2.3,3.2.12,4.1.4,4.2.15,4.2.3,5.0.8,5.1.5,5.2.11,5.2.13,5.2.14,5.2.5
CVSS评分:
BaseScore:8.7 High
Vector:CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
漏洞简述:
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the django.contrib.gis.gdal.GDALRaster constructor. Any value used in a spatial lookup against a GeometryField or RasterField reaches this constructor, including untrusted input, for example a spatial-field filter submitted through the Django admin changelist query string by a staff user with view permission. A dict, or a str holding its JSON representation, is opened in write mode regardless of the constructor s write=False default, allowing a file with an attacker-chosen name and contents to be written through a file-backed GDAL driver. Any other str is treated as a datasource, allowing an outbound network request through a GDAL virtual filesystem handler. Writing a file to a location later imported by the application can result in remote code execution.
漏洞公开时间:2026-08-05 01:16:46
漏洞创建时间:2026-08-05 03:47:00
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2026-15307

更多参考(点击展开)
参考来源 参考链接 来源链接
https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
https://nvd.nist.gov/vuln/detail/CVE-2026-15307
https://www.djangoproject.com/weblog/2026/aug/04/security-releases/
https://docs.djangoproject.com/en/dev/releases/security/
https://bugzilla.redhat.com/show_bug.cgi?id=2511095
https://groups.google.com/g/django-announce
https://www.cve.org/CVERecord?id=CVE-2026-15307
https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
https://security-tracker.debian.org/tracker/CVE-2026-15307

漏洞分析指导链接:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息:

详情(点击展开)
影响的包 修复版本 修复补丁 问题引入补丁 来源
django/django https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520 ljqc
django/django https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6 ljqc
django/django https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa ljqc
django/django https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e ljqc
https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520 cvelistv5
https://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa cvelistv5
https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6 cvelistv5
https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e cvelistv5

二、漏洞分析结构反馈
影响性分析说明:
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the django.contrib.gis.gdal.GDALRaster constructor. Any value used in a spatial lookup against a GeometryField or RasterField can trigger the GDALRaster constructor, which loads the value as an image. This allows a remote attacker to cause an arbitrary file to be loaded into the process memory if they can influence the value of a spatial lookup, leading to a potential information disclosure or denial of service.
openEuler评分:
8.7
Vector:CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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(5.2.17):受影响
2.openEuler-20.03-LTS-SP4(2.2.27):受影响
3.openEuler-22.03-LTS-SP4(4.2.15):受影响
4.openEuler-24.03-LTS-Next(4.2.15):受影响
5.openEuler-24.03-LTS-SP1(4.2.15):受影响
6.openEuler-24.03-LTS-SP3(4.2.15):受影响
7.openEuler-24.03-LTS-SP4(4.2.15):受影响

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

原因说明:
1.master(5.2.17):正常修复
2.openEuler-20.03-LTS-SP4(2.2.27):暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP4(4.2.15):正常修复
4.openEuler-24.03-LTS-Next(4.2.15):正常修复
5.openEuler-24.03-LTS-SP1(4.2.15):正常修复
6.openEuler-24.03-LTS-SP3(4.2.15):正常修复
7.openEuler-24.03-LTS-SP4(4.2.15):正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
25 天前 添加了label:CVE/UNFIXED
openeuler-ci-bot
openeuler-ci-bot成员
25 天前 评论:

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


影响性分析说明:

openEuler评分: (评分和向量)

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

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

原因说明:
1.master(5.2.16):
2.openEuler-20.03-LTS-SP4(2.2.27):
3.openEuler-22.03-LTS-SP4(4.2.15):
4.openEuler-24.03-LTS-Next(4.2.15):
5.openEuler-24.03-LTS-SP1(4.2.15):
6.openEuler-24.03-LTS-SP3(4.2.15):
7.openEuler-24.03-LTS-SP4(4.2.15):


原因说明填写请参考下方表格(注意:版本是否受影响和版本的原因说明必须对应,例如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

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
25 天前 评论:
参考网址 关联pr 状态 补丁链接
https://www.opencve.io/cve/CVE-2026-15307NoneNonehttps://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-15307
https://security-tracker.debian.org/tracker/CVE-2026-15307NoneNonehttps://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-15307
https://nvd.nist.gov/vuln/detail/CVE-2026-15307NoneNonehttps://github.com/django/django/commit/208f80cb682868b584ed0a78f23e4ba6304212aa
https://github.com/django/django/commit/39b3e2d0c743a338def6c473086ebc06865e86b6
https://github.com/django/django/commit/f1949c1f9758947ade984c895ff16bef46f56520
https://github.com/django/django/commit/115ffd0463a765ab1cc93de18e94b5459b8a300e
https://ubuntu.com/security/CVE-2026-15307NoneNonehttps://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

likedislike
openeuler-ci-botopeneuler-ci-bot成员
25 天前 添加了label:sig/sig-python-modules
openeuler-ci-bot
openeuler-ci-bot成员
25 天前 评论:

Welcome To openEuler Community

Hey @openeuler-ci-bot , 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-python-modules ,
and any of the maintainers: @shinwell_hu, @yangzhao_kl ,
and any of the committers: @cherry530, @randy1568, @starlet-dx .

likedislike
此处折叠了49条消息 查看更多
openeuler-ci-bot
openeuler-ci-bot成员
9 天前 评论:

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

状态 分析项目 内容
已分析 1.影响性分析说明 An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.GeoDjango spatial lookups o...
已分析 2.openEulerScore 8.7
已分析 3.openEulerVector AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
已分析 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:暂不修复-暂无解决方案或补丁

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

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9 天前 issue状态由 待办的 改变为 已挂起
xu_ping成员
9 天前 评论:

影响性分析说明:
An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the django.contrib.gis.gdal.GDALRaster constructor. Any value used in a spatial lookup against a GeometryField or RasterField can trigger the GDALRaster constructor, which loads the value as an image. This allows a remote attacker to cause an arbitrary file to be loaded into the process memory if they can influence the value of a spatial lookup, leading to a potential information disclosure or denial of service.

openEuler评分: (评分和向量)
8.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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(5.2.17):受影响
2.openEuler-20.03-LTS-SP4(2.2.27):受影响
3.openEuler-22.03-LTS-SP4(4.2.15):受影响
4.openEuler-24.03-LTS-Next(4.2.15):受影响
5.openEuler-24.03-LTS-SP1(4.2.15):受影响
6.openEuler-24.03-LTS-SP3(4.2.15):受影响
7.openEuler-24.03-LTS-SP4(4.2.15):受影响

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

原因说明:
1.master(5.2.17):正常修复
2.openEuler-20.03-LTS-SP4(2.2.27):暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP4(4.2.15):正常修复
4.openEuler-24.03-LTS-Next(4.2.15):正常修复
5.openEuler-24.03-LTS-SP1(4.2.15):正常修复
6.openEuler-24.03-LTS-SP3(4.2.15):正常修复
7.openEuler-24.03-LTS-SP4(4.2.15):正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9 天前 修改了issue 的描述
openeuler-ci-bot
openeuler-ci-bot成员
9 天前 评论:

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

状态 分析项目 内容
已分析 1.影响性分析说明 An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8.GeoDjango spatial lookups optimistically parse the right-hand-side value as a raster by passing it to the django.contrib.gis.gdal.GDALRaster constructor. Any value used in a spatial lookup against a GeometryField or RasterField can trigger the GDALRaster constructor, which loads the value as an image. This allows a remote attacker to cause an arbitrary file to be loaded into the process memory if they can influence the value of a spatial lookup, leading to a potential information disclosure or denial of service.
已分析 2.openEulerScore 8.7
已分析 3.openEulerVector AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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
已分析 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:正常修复

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

likedislike