Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-54248— Doco-CD has an OCI Trust Policy Bypass via Artifact-Contained Configuration

Quick assessment

Affected
kimdre doco-cd
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Doco-CD 是一款 GitOps 持续交付工具,用于自动部署和更新 Docker Compose 项目/服务以及 Swarm 栈。 在 0.90.1 版本之前,在 OCI 工件(artifact)的校验逻辑中存在一个信任边界缺陷,允许通过工件提供的部署配置影响用于验证该工件本身的信任策略。 漏洞详情: 当通过 启用全局 OCI 签名验证( )时,拥有已配置 OCI 标签(tag)写权限的攻击者,可以发布一个未签名或签名不规范的工件。该工件中包含的 文件若设置了 ,就可以绕过签名验证,导致不可信的部署内容被应用。

CVSS 6.5 · Medium
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-54248

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

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.

Vulnerability Title
Doco-CD has an OCI Trust Policy Bypass via Artifact-Contained Configuration
Source: CVE Program / CVE List V5
Vulnerability Description
Doco-CD is a GitOps continuous delivery tool that automatically deploys and updates Docker Compose projects/services and Swarm stacks. Prior to version 0.90.1, a trust-boundary flaw in OCI artifact verification allowed artifact-provided deployment config to influence the policy used to verify that same artifact. When global OCI signature verification was enabled via `OCI_TRUST_POLICY` (`enabled: true`), an attacker with write access to the configured OCI tag could publish an unsigned or improperly signed artifact containing `.doco-cd.yml` with `oci.verify: false`. This could cause signature verification to be bypassed and untrusted deployment content to be applied. This primarily impacts users deploying from OCI artifacts where deployment config is read from artifact contents (for example, poll/webhook flows without trusted inline deployment overrides). The issue is fixed by enforcing a strict trust boundary and no-downgrade behavior. First, artifact-contained `.doco-cd.yml` is treated as untrusted for OCI trust-policy override decisions. Second, if global `OCI_TRUST_POLICY.enabled` is `true`, per-deployment `oci.verify: false` cannot disable verification. Some workarounds are available. Do not source deployment config from untrusted OCI artifact contents. Use trusted inline `POLL_CONFIG.deployments` and avoid relying on artifact-contained trust-policy overrides. Restrict write/push permissions for OCI repositories/tags used by doco-cd. Prefer immutable digest pinning and protected release/tag workflows. Monitor for unexpected artifact digest changes and failed/suspicious verification events.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
密码学签名的验证不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
kimdre doco-cd < 0.90.1 -

II. Public POCs for CVE-2026-54248

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-54248

登录查看更多情报信息。

Patches & Fixes for CVE-2026-54248 (1)

Vendor Advisories for CVE-2026-54248 (1)

Vendor Pages for CVE-2026-54248 (1)

IV. Related Vulnerabilities

V. Comments for CVE-2026-54248

No comments yet


Leave a comment