在特定的构建方式下,针对 Git 源代码的构建步骤可能会绕过某些策略验证规则。一个恶意的构建定义可以在执行 Git clone 时,使代码库看起来像是来自一个不同于其实际来源的远程 URL。如果策略执行更严格的验证(例如,基于提交 SHA、提交数据或签名等),则所有这些验证仍然会正确生效。
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-93320 | 6.0 MEDIUM | BuildKit improperly handles special files in build snapshots |
| 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