- Veröffentlicht
- 20.11.2026 04:35
- Zuletzt geändert
- 20.11.2026
- EPSS (30 Tage)
- unbekannt
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Beschreibung
Originaltext der Quelle, nicht übersetzt.
### Impact
Logging out of the Argo CD UI deleted the session cookie but did not revoke the session token, and session tokens for local users (including `admin`) had no expiration. Anyone who obtained such a token, for example from a shared machine, browser storage or logs, could keep using it with that user's full permissions after the user logged out, until the user's password was changed.
All versions before v2.0.0 are affected. Only local users with interactive password login, including the built-in `admin` account, are affected; users who log in through SSO are not.
### Patches
A patch for this vulnerability has been released in the following Argo CD version:
* v2.0.0
Session tokens now expire (24 hours by default, configurable with `users.session.duration`), and logging out revokes the token on every API server. The changes were too intrusive to backport to v1.7 or v1.8.
### Workarounds
* Use [SSO](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/#sso) instead of local users.
* [Disable the `admin` account](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/#disable-admin-user) if you don't need it, and disable interactive login for local users that don't need it.
* Change the password of the affected local user. This revokes every token issued to that user before the change, even if you set the same password again.
### Credits
The Argo CD team would like to thank Dimitar Kiryakov and Anatoli Krastev of SAP SE (K8S Delivery Team, BTP Foundational Plane) for responsibly disclosing this issue.
### References
* Fix: [#5477](https://github.com/argoproj/argo-cd/pull/5477) ([6e2ee623f](https://github.com/argoproj/argo-cd/commit/6e2ee623f80b89bf7981c2b8cc20bf84bccb527d))
* [User management](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/)
### 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-cd2.0.0GHSA-86m4-q4hw-93p2
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne 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.