llamaCVEVulnerability Intelligence
/
Advisory · GitHub · Go · github.com/argoproj/argo-cd/v2

GHSA-G3FF-Q88G-CHRJ

Extension proxy RBAC ignores application namespace when applications-in-any-namespace is enabled

Sin parche publicado
Descargar PNG JSON
CVSS 3.1
4.9
Media
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N Fuente: GitHub
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición43 dDesde la divulgación, 7 oct 2026, 10:58 a. m.
Detección42 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
7 oct 26
18 nov 26
19 nov 26
7 oct 26
18 oct 26
29 oct 26
9 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada GHSA-G3FF-Q88G-CHRJ divulgada · CVSS 4.9 (GitHub)
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Impact

Argo CD's proxy extension checks Application `get` before it forwards a request to an extension backend. When applications in any namespace are enabled, that check uses the wrong application name. The namespace is left out, so the policy object is `project/name` instead of `project/namespace/name`. The Application API still uses the three-part name.

All versions from v2.7.0 onward are affected, including every currently supported release. v2.6.15 and earlier do not include this check. The behavior was introduced in 974c2de168 https://github.com/argoproj/argo-cd/commit/974c2de1686521437fa755a180b8d0593e9c0533 (2023-02-15, #11694 https://github.com/argoproj/argo-cd/pull/11694), the change that added authorization to proxy extensions, and was first released in v2.7.0.

Both features have to be turned on. Proxy extensions are off unless `server.enable.proxy.extension` is set. Applications in any namespace are off unless the API server and application controller are started with the extra application namespaces. An install that keeps every Application in the Argo CD namespace is not affected.

An authenticated user who can invoke a proxy extension, and who has Application `get` on `project/name` or on a wildcard such as `project/*`, can invoke that extension against an Application of the same name in another namespace of the same project. A deny rule written as `project/namespace/name` is not evaluated on this path. The Application API still returns a denial for that Application. The extension backend receives the request, the destination cluster name and URL, and the caller's identity.

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 checks the extension request with the Argo CD namespace as the default, which is how the Application API builds the policy object.

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 restores the three-part application check while proxy extensions and applications in any namespace both stay enabled.

  • Leave proxy extensions disabled. They are off by default. To turn them off, do not set `server.enable.proxy.extension` to `true` in `argocd-cmd-params-cm`, and remove `extension.config` from `argocd-cm`. See Proxy extension configuration https://argo-cd.readthedocs.io/en/stable/developer-guide/extensions/proxy-extensions/#configuration.
  • Do not enable applications in any namespace https://argo-cd.readthedocs.io/en/stable/operator-manual/app-any-namespace/. With every Application in the Argo CD namespace, `project/name` is the policy object the rest of the API uses. Namespace-scoped rules are documented in Application in any namespaces https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#application-in-any-namespaces.
  • Limit who can invoke an extension. That does not fix the application check. See The extensions resource https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#the-extensions-resource.
Credits

The Argo CD team would like to thank @komyunghan, @Nadav0077, @akshatgit, @rexpository, @LHeiakim, @edwardav970, @dhki, @arbor-s, and @ninthlife-tools 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: 974c2de1686521437fa755a180b8d0593e9c0533 https://github.com/argoproj/argo-cd/commit/974c2de1686521437fa755a180b8d0593e9c0533 (#11694 https://github.com/argoproj/argo-cd/pull/11694), first released in v2.7.0
  • Applications in any namespace https://argo-cd.readthedocs.io/en/stable/operator-manual/app-any-namespace/
  • Proxy extensions https://argo-cd.readthedocs.io/en/stable/developer-guide/extensions/proxy-extensions/
  • Application in any namespaces https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#application-in-any-namespaces
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
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · GitHub
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:H
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:C
CambiadoSin cambio
ConfidencialidadC:L
AltoBajoNinguno
IntegridadI:L
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida Última
github.com/argoproj/argo-cd/v2≥ 2.7.0
github.com/argoproj/argo-cd/v3≥ 3.0.0
2.7.0
v2.14.21
3.0.0
v3.6.1
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
gogithub.com/argoproj/argo-cd/v2
Sin parche — — v2.14.21 afectada
gogithub.com/argoproj/argo-cd/v3
Sin parche — — v3.6.1 afectada
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Advisoryhttps://github.com/argoproj/argo-cd/security/advisories/GHSA-g3ff-q88g-chrj

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.