目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1336

100%

CVE-2026-86861— pgAdmin 4 文件管理器符号链接绕过漏洞

一分钟漏洞结论

影响对象
pgadmin.org pgAdmin 4
利用判断
尚无明确在野利用证据,仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本;无法立即升级时,限制受影响服务暴露并加强监测。

以下是该漏洞描述的中文翻译: pgAdmin 4 文件管理器(File Manager)的 端点,用于支持查询工具(Query Tool)和 ERD 中的保存操作。该端点通过 验证请求的路径,随后使用普通的 调用以写模式打开文件。此前,CVE-2026-7819 已通过使用 标志加固了独立的文件上传路径,使内核拒绝跟随最终路径组件上的符号链接;但 路径仍保留在未受保护的 调用上。若在执行权限检查时已存在的符号链接会被检查逻辑本身拒绝;剩余的暴露风险在于:在检查与写入之间的时间窗口内,最终路径组件处的符号链接被替换,

CVSS 5.9 · Medium

可能的 ATT&CK 技术 1 AI

T1078 · Valid Accounts
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2026-86861 基础信息

漏洞信息

对漏洞内容有疑问?看看神龙的深度分析是否有帮助!
查看神龙十问 ↗

尽管我们使用了先进的大模型技术,但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性,但请您根据实际情况进行核实和判断。

Vulnerability Title
pgAdmin 4: File Manager save_file writes through a symbolic link planted after the containment check
来源: CVE Program / CVE List V5
Vulnerability Description
pgAdmin 4's File Manager save_file endpoint, which backs saving from the Query Tool and ERD, validated the requested path with Filemanager.check_access_permission() and then opened the file for writing with a plain open() call. CVE-2026-7819 had previously hardened the separate file upload path by opening its target with O_NOFOLLOW, so that the kernel refuses to follow a symbolic link at the final path component, but save_file was left on an unprotected open(). A symbolic link already present when the check ran was rejected by the check itself; the remaining exposure was a link substituted at the final path component in the interval between the check and the write, at which point the write followed the link and landed outside the user's storage directory, creating or overwriting an arbitrary file as the operating-system account running pgAdmin. Exploitation requires the ability to create or replace a symbolic link inside the requesting user's storage directory. pgAdmin exposes no interface that creates symbolic links, so this requires filesystem access to the pgAdmin host or to a shared or network-mounted storage backend, together with winning the timing window. The reporter did not achieve a write against a released version, having attempted approximately 63,000 racing requests without success; the reported defect is the uncovered write path rather than a demonstrated sandbox escape. The fix routes save_file's write through the same O_NOFOLLOW-protected helper already used by the upload path, so both File Manager write sinks carry identical kernel-enforced protection, and reports a symbolic-link refusal explicitly instead of surfacing the underlying system error text. Note that files created by save_file are now given mode 0600, inheriting the behaviour introduced for uploads. The protection covers the final path component; substitution of an intermediate directory component is not addressed by this change. This issue affects pgAdmin 4: from the introduction of the containment check in the File Manager save path before 9.18.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L
来源: CVE Program / CVE List V5
Vulnerability Type
检查时间与使用时间(TOCTOU)的竞争条件
来源: CVE Program / CVE List V5

受影响产品

厂商 产品 影响版本 CPE 订阅
pgadmin.org pgAdmin 4 0 ~ 9.18 -

二、漏洞 CVE-2026-86861 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2026-86861 的情报信息

登录查看更多情报信息。

CVE-2026-86861 其他参考 (1)

同批安全公告 · pgadmin.org · 2026-09-17 · 共 4 条

CVE-2026-86863 9.8 CRITICAL pgAdmin 4 Web服务器身份验证绕过漏洞
CVE-2026-86864 8.8 HIGH pgAdmin 4 备份工具参数注入漏洞
CVE-2026-86862 6.5 MEDIUM pgAdmin 4 数据库连接字符串注入漏洞

IV. Related Vulnerabilities

V. Comments for CVE-2026-86861

暂无评论


发表评论