CVE-2026-54526

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% 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, nvd
Trending — 3 sources updated this weekElevated
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: Elevated riskExposed: 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
9.9
EG Score
9.9(medium)
EG Risk
61(Track*)
EG Risk 61/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
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 30, 2026

Advisory Details (5)

Auto-updated Jul 30, 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 14× in last 7d / 27× 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-30 19:10 UTCEG score recompute
  2. 2026-07-30 16:28 UTCEPSS rescore
  3. 2026-07-30 14:50 UTCEG score recompute▲ 1.00
  4. 2026-07-30 14:48 UTCNVD updateCVSS v3 → 9.9 · severity → CRITICAL
  5. 2026-07-30 02:26 UTCEG score recompute
  6. 2026-07-30 01:30 UTCEPSS rescore
  7. 2026-07-29 01:33 UTCEG score recompute
  8. 2026-07-28 15:37 UTCEPSS rescore
  9. 2026-07-28 00:43 UTCEG score recompute
  10. 2026-07-26 23:52 UTCEG score recompute
  11. 2026-07-26 14:54 UTCEPSS rescore
  12. 2026-07-26 11:25 UTCEG score recompute
  13. 2026-07-25 14:18 UTCEPSS rescore
  14. 2026-07-24 14:18 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 03:19 UTCEG score recompute
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-21 15:25 UTCEPSS rescore
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 14:31 UTCEPSS rescore
  21. 2026-07-19 14:31 UTCEPSS rescore
  22. 2026-07-19 02:34 UTCEG score recompute
  23. 2026-07-19 02:29 UTCEPSS rescore
  24. 2026-07-18 10:04 UTCEPSS rescore
  25. 2026-07-17 14:13 UTCEG score recompute
Show 2 more
  1. 2026-07-16 19:15 UTCEG score recompute
  2. 2026-07-16 19:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54526?
CVE-2026-54526 is a critical 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, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54526 actively exploited?
CVE-2026-54526 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 84.0% of all scored CVEs.
What is the CVSS score of CVE-2026-54526?
CVE-2026-54526 has a CVSS v3 base score of 9.9 (NVD).
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