CVE-2026-113709

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th 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-105250 (ENISA EUVD)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.1.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, when an operator has enabled --enable-helm for kustomize build, helmGlobals.configHome can point Helm's config and data directories at a repository-controlled location. Helm automatically loads a downloader plugin from /.data/plugins without a separate plugin-install step and executes its program inside argocd-repo-server when a helmCharts repository URL uses the plugin's protocol. The command runs as the repo-server user and can read repository credentials and other process-accessible data. An attacker can commit the Kustomization and plugin to a Git repository that an Application builds or upload the files through POST /api/v1/applications/manifestsWithFiles, also exposed by argocd app diff --local --server-side-generate. The upload path requires only Application get permission on an existing Application, without Application update or sync permission or repository write access. Both delivery paths require prior operator enablement of --enable-helm; deployments that do not enable it are not affected. Kustomize 4.1.0 first passed helmGlobals.configHome through to Helm. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.5%
EPSS %ILE
44th
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

October 20, 2026

Last Modified

October 21, 2026

Advisory Details (10)

Auto-updated Oct 30, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub pull request Patch Available

Add flag --enable-helm

Patch available: kubernetes-sigs/kustomize kyaml/v0.18.1 (PR #3784 merged 2021-04-12)

https://github.com/kubernetes-sigs/kustomize/pull/3784
GitHub advisoryMentions a patch (unverified)

Command injection via a repository proxy URL on SSH Git repositories · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-j6cw-g6p4-7hch
GitHub advisoryMentions a patch (unverified)

A Kustomize Helm config home can run commands in the repo-server · Advisory · argoproj/argo-cd · GitHub

https://github.com/argoproj/argo-cd/security/advisories/GHSA-fw5c-w8rc-j7fx
GitHub release Patch Available

v3.6.0-rc2

Patch available: argoproj/argo-cd v3.6.0-rc2 (pre-release)

https://github.com/argoproj/argo-cd/releases/tag/v3.6.0-rc2
GitHub release Patch Available

v3.5.4

Patch available: argoproj/argo-cd v3.5.4

https://github.com/argoproj/argo-cd/releases/tag/v3.5.4
GitHub release Patch Available

v3.4.10

Patch available: argoproj/argo-cd v3.4.10

https://github.com/argoproj/argo-cd/releases/tag/v3.4.10
GitHub release Patch Available

v3.3.15

Patch available: argoproj/argo-cd v3.3.15

https://github.com/argoproj/argo-cd/releases/tag/v3.3.15
GitHub pull request

fix: upgrade to kustomize 4.1.2

Fix merged in argoproj/argo-cd PR #6059 on 2021-04-20 — awaiting tagged release

https://github.com/argoproj/argo-cd/pull/6059
GitHub commit

commit b6d5c23bce2f (argoproj/argo-cd)

Fix landed in argoproj/argo-cd commit b6d5c23bce2f — awaiting tagged release

https://github.com/argoproj/argo-cd/commit/b6d5c23bce2f8a46c52975ba438a3b93d242d96c
Web page

Kustomize - Argo CD - Declarative GitOps CD for Kubernetes

https://argo-cd.readthedocs.io/en/stable/user-guide/kustomize/#kustomizing-helm-charts

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 24× 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-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-30 10:53 UTCEG score recompute
  3. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-29 11:42 UTCEG score recompute
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-28 12:32 UTCEG score recompute
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-27 13:20 UTCEG score recompute
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-26 13:43 UTCEG score recompute
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-25 14:11 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  14. 2026-10-24 15:00 UTCEG score recompute
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  16. 2026-10-23 15:50 UTCEG score recompute
  17. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  18. 2026-10-22 16:31 UTCEG score recompute
  19. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  20. 2026-10-21 16:28 UTCEG score recompute
  21. 2026-10-21 16:01 UTCEG score recompute
  22. 2026-10-20 19:25 UTCEG score recompute
  23. 2026-10-20 18:30 UTCEG score recomputeFirst assessed: 9.9 CRITICAL
  24. 2026-10-20 18:27 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-113709?
CVE-2026-113709 is a critical-severity vulnerability; its CVE record was published on October 20, 2026. Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.1.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, when an operator has enabled --enable-helm for kustomize build, helmGlobals.configHome can point Helm's config and data directories at a repository-controlled location.…
When was the CVE record for CVE-2026-113709 published?
The CVE record for CVE-2026-113709 was published on October 20, 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 October 21, 2026; the record at its source may have been updated since.
Is CVE-2026-113709 actively exploited?
CVE-2026-113709 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113709?
CVE-2026-113709 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-113709?
A fix for CVE-2026-113709 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-113709

Explore →

Is Your Infrastructure Affected by CVE-2026-113709?

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

Book a Demo →Browse All CVEs