CVE-2026-54248

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 14, 2026

Advisory Details (3)

Auto-updated Sep 11, 2026
Patch available. Sources: github_release, github, github_pr.
github_release Patch Available

v0.90.1

Patch available: kimdre/doco-cd v0.90.1

https://github.com/kimdre/doco-cd/releases/tag/v0.90.1
github_pr Patch Available

fix(oci): prevent policy downgrades when trust policy is enabled globally

Patch available: kimdre/doco-cd v0.101.0 (PR #1407 merged 2026-06-03)

https://github.com/kimdre/doco-cd/pull/1407
github Patch Available

OCI Trust Policy Bypass via Artifact-Contained Configuration · Advisory · kimdre/doco-cd · GitHub

https://github.com/kimdre/doco-cd/security/advisories/GHSA-5rv3-qpp3-6jp5

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 10:49 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 12:32 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 15:54 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 17:38 UTCEG score recompute
  9. 2026-09-14 19:21 UTCEG score recompute
  10. 2026-09-14 18:40 UTCEG score recompute
  11. 2026-09-13 19:01 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-12 20:44 UTCEG score recompute
  14. 2026-09-11 22:27 UTCEG score recompute
  15. 2026-09-11 21:34 UTCEG score recompute
  16. 2026-09-11 21:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54248?
CVE-2026-54248 is a medium vulnerability published on September 11, 2026. 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…
When was CVE-2026-54248 disclosed?
CVE-2026-54248 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54248 actively exploited?
CVE-2026-54248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54248?
CVE-2026-54248 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-54248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54248, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54248

Explore →

Is Your Infrastructure Affected by CVE-2026-54248?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs