BuildKit 可能会被诱骗,在处理特殊文件 inode 时执行文件操作,而正常情况下应针对普通文件进行这些操作。特殊文件可能导致操作阻塞;在具有 root 权限的工作器(rootful workers)中,还可能引发对主机设备的未预期访问。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-93318 | 7.5 HIGH | Cache poisoning via unvalidated image layer DiffIDs |
| CVE-2026-93316 | 7.1 HIGH | Starting daemon with --cdi-disabled flag can lead to panic on specific builds |
| CVE-2026-93322 | 6.9 MEDIUM | Malformed MergeOp can crash the BuildKit daemon |
| CVE-2026-93323 | 6.8 MEDIUM | Oversized Dockerfile or .dockerignore can exhaust buildkitd memory |
| CVE-2026-93326 | 6.0 MEDIUM | Crafted Git build source can bypass certain policy validation |
| CVE-2026-93317 | 5.9 MEDIUM | Container blob cache can accept unverified content |
| CVE-2026-93319 | 5.7 MEDIUM | A malicious frontend can cause a daemon panic |
No comments yet