CVE-2026-82277
Description
A missing-authentication flaw (CWE-306) was found in the Argo Rollouts dashboard. The dashboard binds to all network interfaces (0.0.0.0) and exposes mutating Rollout operations — including PromoteRollout, AbortRollout, RestartRollout, SetRolloutImage, UndoRollout, and RetryRollout — without any authentication, authorization, or CSRF protection. An attacker with network access to the dashboard port can invoke these operations against any Rollout in the namespaces reachable through the operator's kubeconfig, allowing unauthorized promotion, rollback, restart, or image modification of workloads. This can lead to a complete compromise of the integrity and availability of managed application rollouts.
Statement
A CRITICAL missing-authorization flaw (CWE-306) was found in the Argo Rollouts dashboard as shipped in the argo-rollouts container images of Red Hat OpenShift GitOps. The dashboard binds to all network interfaces (0.0.0.0) and exposes mutating Rollout operations — including PromoteRollout, AbortRollout, RestartRollout, SetRolloutImage, UndoRollout, and RetryRollout — without authentication, authorization, or CSRF protection. An attacker with network access to the dashboard port can invoke these operations against any Rollout in the namespaces reachable through the operator's kubeconfig, allowing unauthorized promotion, rollback, restart, or image modification of workloads and compromising the integrity and availability of managed application rollouts. Within Red Hat OpenShift GitOps, the argo-rollouts container images are the affected components; the gitops-rhel9-operator container images in the gitops-1.20 through gitops-1.22 streams are not affected because the vulnerable dashboard is not present in them. Remediation is delegated to the OpenShift GitOps business unit: fixes for the argo-rollouts container have been delivered in the gitops-1.20 through gitops-1.22 streams, while the older gitops-1.19 stream has a delegated wontfix resolution. Red Hat rates this flaw CRITICAL with a CVSS 3.1 base score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); the CVEORG CVSS 4.0 score of 9.3 is also Critical, and the difference reflects the CVSS version used rather than a material difference in severity.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. For the Red Hat OpenShift GitOps streams where a fix for the argo-rollouts container has been delivered, users should apply the updated images through their usual update channels.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 9.8 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
