### Impact
Argo CD runs a shell command in the repo-server when it clones or fetches an SSH Git repository that has a proxy URL. The proxy host and port are copied into an SSH `ProxyCommand`. A host that contains shell metacharacters breaks out of that command and runs in the repo-server.
All versions from v2.11.0 onward are affected, including every currently supported release. v2.10.20 and earlier are not. The behavior was introduced in [9b27aeb1a4](https://github.com/argoproj/argo-cd/commit/9b27aeb1a4fb15d11a0f01cad65dea1fdfc60205) (2024-01-09, [#15864](https://github.com/argoproj/argo-cd/pull/15864)), the change that added SOCKS5 proxy support for SSH Git URLs, and was first released in v2.11.0.
The repository must use SSH. `http`, `https`, and `socks5` proxy URLs all take this path when they are set on an SSH repository. An HTTPS Git repository uses the proxy as an HTTP proxy and does not build this command.
Anyone who can create or update a repository or a repository credential template can set the proxy. That includes a project-scoped repository permission, `argocd repo add --proxy`, and a repository Secret. A credential template applies its proxy to every matching SSH repository that does not have its own credentials. Argo CD runs the command when it tests the repository connection and on later fetches. The process can read other Git, Helm, and OCI credentials stored for the repo-server.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v3.6.0-rc2
* v3.5.4
* v3.4.10
* v3.3.15
The fix stops passing the proxy host and port through a shell.
Argo CD 2.x and 3.0 through 3.2 are out of support and will not receive a patch. Upgrade to a patched 3.3 or newer release.
### Workarounds
There is no setting that keeps SSH repository proxies and removes the shell command.
* Do not grant repository create or update to untrusted users, including project-scoped repository access. See [RBAC resources](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-model-structure) and [project-scoped repositories](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#project-scoped-repositories-and-clusters).
* Do not set a proxy on an SSH repository or on a credential template that matches SSH repositories. The proxy field is documented in [Configure repositories with proxy](https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#configure-repositories-with-proxy). Credential templates are documented in [Credential templates](https://argo-cd.readthedocs.io/en/stable/user-guide/private-repositories/#credential-templates). The `--proxy` flag is documented in [`argocd repo add`](https://argo-cd.readthedocs.io/en/stable/user-guide/commands/argocd_repo_add/).
An HTTPS Git repository with an HTTP proxy does not use this command. Review existing repository and credential-template Secrets for unexpected `proxy` values.
### Credits
The Argo CD team would like to thank @kamil-sawicki, @yuvalelarat, @cherez0ff, @McCaulay, @gehan-psbc, @ria-labs-security, @parameter-ai-security, and @zwindler for responsibly disclosing this issue according to our [security reporting guidelines](https://github.com/argoproj/argo-cd/blob/master/SECURITY.md#reporting-a-vulnerability).
### References
* Introducing commit: [9b27aeb1a4fb15d11a0f01cad65dea1fdfc60205](https://github.com/argoproj/argo-cd/commit/9b27aeb1a4fb15d11a0f01cad65dea1fdfc60205) ([#15864](https://github.com/argoproj/argo-cd/pull/15864)), first released in v2.11.0
* [Configure repositories with proxy](https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#configure-repositories-with-proxy)
### For more information
* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd
A vulnerability in Borewit music-metadata versions before 11.15.0 causes an unhandled exception leading to a process crash. The issue arises from an un-awaited asynchronous call when skipping unrecognized chunks in DSF audio files, which can result in a negative argument passed to a function that throws a RangeError. This error occurs after the main parsing promise resolves, making it uncatchable by typical try/catch error handling. The impact is a denial-of-service (DoS) condition where a single crafted DSF file can crash the Node.js process using music-metadata, affecting availability.
music-metadata version 11.15.0 contains a vulnerability in its APEv2 tag parser where it allocates memory based on an untrusted size value without verifying that the declared size fits within the actual file data. This can lead to excessive memory allocation and potential denial of service. The issue is limited to availability impact and does not affect confidentiality or integrity. The vulnerability is fixed in versions after 11.15.0.
CVE-2026-15781 is a high-severity stack-based buffer overflow vulnerability in IBM DataPower Gateway versions 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. This flaw allows a remote authenticated attacker to execute arbitrary code on the affected systems. The vulnerability requires high attack complexity and privileges, with no user interaction needed. It impacts confidentiality, integrity, and availability of the system. No explicit patch or remediation information is provided in the source data.
CVE-2026-15784 is a high-severity vulnerability in IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. It involves an out-of-bounds write that could allow a remote attacker to execute arbitrary code without user interaction. The vulnerability has a CVSS 3.1 score of 8.1, indicating a significant risk to confidentiality, integrity, and availability. No information about patches or vendor advisories is provided, so the patch status is not confirmed.
CVE-2026-15762 is a critical vulnerability in IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.0.0 through 10.6.0.10, 10.6.1 through 10.6.6, and 11.0.0.0 through 11.0.0.2. It involves an out-of-bounds write that could allow a remote attacker to execute arbitrary code without authentication or user interaction.
IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2 could allow a remote attacker to cause a denial of service due to out-of-bounds memory access caused by a strict-weak-ordering violation in a sorting comparator.
IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2 could allow a remote attacker to cause a denial of service due to a heap-based buffer overflow.
IBM DataPower Gateway 10.5.0.0 through 10.5.0.22, 10.6.1 through 10.6.6, 10.6.0.0 through 10.6.0.10, and 11.0.0.0 through 11.0.0.2 could allow a remote attacker to obtain sensitive information and cause a denial of service due to an out-of-bounds write.
CVE-2026-76272 affects Splunk Enterprise and Splunk Secure Gateway where authorization checks are missing for certain actions. Users without admin or power roles can cause Splunk Secure Gateway to sign attacker-controlled payloads due to lack of verification. This vulnerability affects multiple versions of Splunk Enterprise below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, as well as Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72. The CVSS score is 4.3, indicating a medium severity impact. No known exploits are reported in the wild. The vulnerability allows integrity impact but no confidentiality or availability impact.
CVE-2026-76265 is a medium severity vulnerability in Splunk Enterprise and Splunk Secure Gateway where users without admin or power roles can access privileged functionality. This occurs because certain REST API endpoints in Splunk Secure Gateway do not properly enforce authorization checks. Exploiting this, an unauthorized user could cause the gateway to sign attacker-controlled payloads. The issue affects multiple versions of Splunk Enterprise below 10.4.3, 10.2.7, 10.0.10, and 9.4.15, as well as Splunk Secure Gateway versions below 3.10.11, 3.9.25, and 3.8.72.
CVE-2026-107224 is an integer overflow vulnerability in the qax-os excelize library affecting versions from 2.1.0 through 2.11.0. It arises from improper handling of Zip64 uncompressed sizes that, when set to values with the high bit set, cast to negative int64 values. This bypasses unzip size guards and leads to a panic due to a negative capacity passed to Go's make function, causing a runtime error and crashing the calling goroutine. The vulnerability can be triggered by a crafted 159-byte archive without authentication.
CVE-2026-107215 is a high-severity vulnerability in the qax-os excelize Go library for Microsoft Excel spreadsheets. Versions from 2.3.1 up to and including 2.11.0 improperly allocate memory based on attacker-controlled size values from OLE compound file streams without proper validation. This can lead to excessive memory allocation or negative length allocations, causing process crashes or memory exhaustion. No patch or fixed version is currently available.
CVE-2026-107159 is a divide-by-zero vulnerability in miniupnpd up to version 2.3.11 when built with the --strict option. This flaw occurs in the ProcessSSDPData() function and can be triggered by unauthenticated local network attackers sending a multicast M-SEARCH datagram with MX: 0 and a known ST to port 1900. Exploitation causes the daemon to crash, resulting in denial of UPnP IGD service.
CVE-2026-79818 is a medium severity vulnerability in Hewlett Packard Enterprise ClearPass Policy Manager (CPPM). It involves an API interface flaw that allows an unauthenticated remote attacker to bypass authentication controls. Exploiting this vulnerability could enable the attacker to access sensitive information from the affected system. The vulnerability affects specific versions of CPPM, including 6.11.0 through 6.11.15 and version 6.14.0. No known exploits are reported in the wild, and no patch information is provided.
CVE-2026-79816 is a medium severity vulnerability in Hewlett Packard Enterprise ClearPass Policy Manager (CPPM) that allows an unauthenticated remote attacker to perform a DOM-based cross-site scripting (XSS) attack via a client interface. Exploitation could enable execution of arbitrary script code in the victim's browser within the affected interface. The affected versions are 6.11.0 through 6.11.15 and exactly 6.14.0. No known exploits are reported in the wild. No patch or remediation information is provided in the available data.
CVE-2026-79815 is a command injection vulnerability in the OnGuard agent of Hewlett Packard Enterprise's ClearPass Policy Manager (CPPM). It allows an authenticated remote attacker to inject arbitrary commands, potentially executing them with elevated privileges on the affected Windows endpoint. The vulnerability affects specific versions of CPPM, including 6.11.0 through 6.11.15 and version 6.14.0. The CVSS 3.1 base score is 6.5, indicating a medium severity level.
CVE-2026-79812 is a denial of service vulnerability in the OnGuard agent of Hewlett Packard Enterprise ClearPass Policy Manager (CPPM). An authenticated local attacker could exploit this flaw to disrupt the normal operation of the agent service. The vulnerability affects specific versions of CPPM, including 6.11.0 through 6.11.15 and version 6.14.0. The CVSS v3.1 base score is 6.1, indicating a medium severity impact primarily due to availability disruption.
CVE-2026-79811 is a high-severity SQL injection vulnerability in Hewlett Packard Enterprise's ClearPass Policy Manager (CPPM) API. It allows a remote authenticated attacker with administrative privileges to execute arbitrary database commands. The vulnerability affects specific versions of CPPM including 6.11.0 through 6.11.15 and 6.14.0. No known exploits are reported in the wild, and no patch information is provided in the source data.
CVE-2026-79810 is a high-severity remote code execution vulnerability in Hewlett Packard Enterprise ClearPass Policy Manager (CPPM). It affects authenticated users with high privileges, allowing them to execute arbitrary commands on the underlying operating system. The vulnerability impacts versions 6.11.0 through 6.11.15 and version 6.14.0. No patch information is provided in the available data. The CVSS score is 7.2, indicating significant impact on confidentiality, integrity, and availability.