{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54248 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54248 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54248 is a medium-severity vulnerability in kimdre doco-cd, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54248 and fix it if it is affected.\n\nWhat it is: CVE-2026-54248 is a medium-severity vulnerability in kimdre doco-cd, published on 11 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54248 in the wild and no public exploit code.\n\nAffected product: kimdre doco-cd. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54248/ (Markdown: https://insights.sbomify.com/CVE-2026-54248/index.md)","id":"CVE-2026-54248","markdown":"https://insights.sbomify.com/CVE-2026-54248/index.md","name":"CVE-2026-54248","record":{"aliases":["GHSA-5rv3-qpp3-6jp5"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"GitOps CD tool","requires_auth":"high_privilege","summary":"Attackers can bypass OCI signature verification in Doco-CD by embedding malicious config in artifacts, allowing untrusted code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-501","name":"Trust Boundary Violation"},{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Doco-CD has an OCI Trust Policy Bypass via Artifact-Contained Configuration","id":"CVE-2026-54248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Pydantic AI: Unvalidated UploadedFile references in UI adapters allow server-side file access using the application's credentials","id":"CVE-2026-54249"},"packages":[],"prev":{"headline":"Skipper: Unbounded Request Body Read in Admission Webhook Causes Memory Exhaustion DoS","id":"CVE-2026-54247"},"products":["doco-cd"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["kimdre"]},"summary":"Attackers can bypass OCI signature verification in Doco-CD by embedding malicious config in artifacts, allowing untrusted code execution.","url":"https://insights.sbomify.com/CVE-2026-54248/"}