CVE-2026-54526

HIGHPre-NVD 8.98.9
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:github_m
8.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.9Exploit: NoneExposed: 0

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

Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 3.7.15 and 4.0.6, the allow-list fix for CVE-2026-31892 is incomplete because workflow/util/merge.go ValidateUserOverrides and SanitizeUserWorkflowSpec walk only the top-level fields of WorkflowSpec via reflection, and WorkflowSpec.ArtifactGC is allow-listed wholesale; the struct behind that field, WorkflowLevelArtifactGC, has a PodSpecPatch sub-field whose contents flow unmodified into util.ApplyPodSpecPatch on the artifact-GC pod, the same sink the original fix closed for WorkflowSpec.PodSpecPatch, so a user submitting a Workflow under templateReferencing: Strict or Secure (against a referenced WorkflowTemplate that declares an output artifact and setting spec.artifactGC.strategy: OnWorkflowCompletion) can still inject an arbitrary strategic merge patch into the artifact-GC pod, including hostPath volumes, privileged: true, arbitrary image and command, and hostNetwork: true, defeating the stated purpose of Strict/Secure reference mode. This issue is fixed in versions 3.7.15 and 4.0.6.

CVSS v3
8.9
EG Score
8.9(low)
EPSS
—
KEV
Not listed

Published

July 16, 2026

Last Modified

July 16, 2026

Advisory Details (5)

Auto-updated Jul 16, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Incomplete fix for CVE-2026-31892 / GHSA-3775-99mw-8rp4: ArtifactGC.PodSpecPatch bypass of Strict/Secure templateReferencing · Advisory · argoproj/argo-workflows · GitHub

https://github.com/argoproj/argo-workflows/security/advisories/GHSA-48p8-g2fx-3wwm
github_release Patch Available

v4.0.6

Patch available: argoproj/argo-workflows v4.0.6

https://github.com/argoproj/argo-workflows/releases/tag/v4.0.6
github_release Patch Available

v3.7.15

Patch available: argoproj/argo-workflows v3.7.15

https://github.com/argoproj/argo-workflows/releases/tag/v3.7.15
github_commit

commit 358cc3968c8f (argoproj/argo-workflows)

Fix landed in argoproj/argo-workflows commit 358cc3968c8f — awaiting tagged release

https://github.com/argoproj/argo-workflows/commit/358cc3968c8f06f1be0967e41df191088db0b662
github_commit

commit 277e9cef0ad1 (argoproj/argo-workflows)

Fix landed in argoproj/argo-workflows commit 277e9cef0ad1 — awaiting tagged release

https://github.com/argoproj/argo-workflows/commit/277e9cef0ad16d7eaaab253573d0695951a65dbd

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 2× 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-07-16 19:15 UTCEG score recompute
  2. 2026-07-16 19:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-54526?
CVE-2026-54526 is a high vulnerability published on July 16, 2026. Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Prior to 3.7.15 and 4.0.6, the allow-list fix for CVE-2026-31892 is incomplete because workflow/util/merge.go ValidateUserOverrides and SanitizeUserWorkflowSpec walk only the top-level…
When was CVE-2026-54526 disclosed?
CVE-2026-54526 was first published in the National Vulnerability Database on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-54526?
CVE-2026-54526 has a CVSS v3 base score of 8.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54526?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54526, 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-54526

Explore →

Is Your Infrastructure Affected by CVE-2026-54526?

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

Start Free Scan →Browse All CVEs