← Übersicht Argo CD

Secret masking is skipped when last-applied-configuration is not valid JSON (incomplete fix for CVE-2026-45737)

GHSA-jj8j-82j2-7ph7

Mittel · CVSS 6.3 Netzwerk · mit Login Fix verfügbar

Veröffentlicht
20.11.2026 05:04
Zuletzt geändert
20.11.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

### Impact The fix for [GHSA-rg3g-4rw9-gqrp](https://github.com/argoproj/argo-cd/security/advisories/GHSA-rg3g-4rw9-gqrp) (CVE-2026-45737) masks Secret values stored in the `kubectl.kubernetes.io/last-applied-configuration` annotation before showing diffs. It only did so when the annotation contained valid JSON. If a Secret's annotation could not be parsed, the masking step was skipped and the annotation, including any plaintext `data` or `stringData` values in it, was returned unmasked. Users who can view the Application's diff, including through server-side diff, could read those values. The affected versions are those that include the CVE-2026-45737 fix but not this one: v3.2.12 and later 3.2 releases, v3.3.10 through v3.3.13, v3.4.2 through v3.4.6, and v3.5.0. Earlier versions are affected by CVE-2026-45737 itself. An attacker needs permission to view the Application, and the live Secret must carry a `last-applied-configuration` annotation that isn't valid JSON. ### Patches A patch for this vulnerability has been released in the following Argo CD versions: * v3.6.0 * v3.5.1 * v3.4.7 * v3.3.14 Secret masking now fails closed: an annotation that can't be parsed is replaced entirely. ### Workarounds * Remove the `kubectl.kubernetes.io/last-applied-configuration` annotation from Secrets, or manage them with [server-side apply](https://argo-cd.readthedocs.io/en/stable/user-guide/sync-options/#server-side-apply), which doesn't add it. * Limit who can view Applications that manage Secrets using [RBAC](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/). ### Credits The Argo CD team would like to thank @MarwenOnGit for responsibly disclosing this issue. The Argo CD team also found and fixed it independently; thanks to @pjiang-dev and @agaudreault for the fix. ### References * Fix: [994e271bc](https://github.com/argoproj/argo-cd/commit/994e271bcc3c591540bbe778bf09df303dcbf5f7) ([#28989](https://github.com/argoproj/argo-cd/pull/28989)) * Incomplete fix of: [GHSA-rg3g-4rw9-gqrp](https://github.com/argoproj/argo-cd/security/advisories/GHSA-rg3g-4rw9-gqrp) (CVE-2026-45737) ### 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

Betroffene Pakete im beobachteten Stack

Gogithub.com/argoproj/argo-cd/v33.3.0 || >= 3.3.10, 3.3.0 → 3.3.14 || >= 3.4.2, 3.4.0 → 3.5.1GHSA-jj8j-82j2-7ph7

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · mit Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.