CVE-2026-54248

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-76757 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 30, 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 pull request 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 advisoryMentions a patch (unverified)

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 8× in last 7d / 46× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-30 11:25 UTCOSV refresh
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-25 14:19 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-22 21:23 UTCEG score recompute
  14. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-18 03:31 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 57 more
  1. 2026-10-12 15:56 UTCEG score recompute
  2. 2026-10-11 19:39 UTCEG score recompute
  3. 2026-10-11 16:55 UTCEG score recompute
  4. 2026-10-11 14:18 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-11 06:47 UTCEG score recompute
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-10 04:18 UTCEG score recompute
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-09 05:54 UTCEG score recompute
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-08 07:37 UTCEG score recompute
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-07 09:20 UTCEG score recompute
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-06 10:58 UTCEG score recompute
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-05 12:42 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-03 15:53 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-02 17:28 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-30 15:21 UTCEG score recompute
  26. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-09-29 17:04 UTCEG score recompute
  28. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  29. 2026-09-27 19:25 UTCEG score recompute
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  31. 2026-09-26 21:05 UTCEG score recompute
  32. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  33. 2026-09-25 00:29 UTCEG score recompute
  34. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  35. 2026-09-24 02:12 UTCEG score recompute
  36. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-09-23 03:56 UTCEG score recompute
  38. 2026-09-22 05:40 UTCEG score recompute
  39. 2026-09-21 07:22 UTCEG score recompute
  40. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-09-20 09:06 UTCEG score recompute
  42. 2026-09-19 10:49 UTCEG score recompute
  43. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-09-18 12:32 UTCEG score recompute
  45. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-09-16 15:54 UTCEG score recompute
  47. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  49. 2026-09-15 17:38 UTCEG score recompute
  50. 2026-09-14 19:21 UTCEG score recompute
  51. 2026-09-14 18:40 UTCEG score recompute
  52. 2026-09-13 19:01 UTCEG score recompute
  53. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  54. 2026-09-12 20:44 UTCEG score recompute
  55. 2026-09-11 22:27 UTCEG score recompute
  56. 2026-09-11 21:34 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
  57. 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-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-54248 published?
The CVE record for CVE-2026-54248 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-54248 actively exploited?
CVE-2026-54248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54248?
CVE-2026-54248 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54248?
A fix for CVE-2026-54248 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs