A critical vulnerability in the Argo Rollouts dashboard allows unauthenticated attackers to remotely trigger destructive or disruptive rollout operations, posing a severe risk to application availability.

The vulnerability stems from a lack of authentication, authorization, and CSRF protection on the dashboard API, which binds to all network interfaces. An unauthenticated attacker can invoke sensitive functions including PromoteRollout, AbortRollout, and SetRolloutImage.

The ability to manipulate rollout operations without authentication allows an attacker to force unauthorized deployments, abort legitimate updates, or revert production environments to unstable states. With a CVSS score of 9.8, this flaw represents a critical threat to service integrity and business continuity, as it facilitates direct interference with the software delivery pipeline.

Immediate Action: Upgrade to a version of Argo Rollouts that includes authentication and authorization controls for the dashboard API. If an immediate update is not feasible, restrict network access to the dashboard interface to trusted management networks only.

Proactive Monitoring: Review Kubernetes audit logs and Argo Rollouts access logs for suspicious API calls originating from unauthorized or unexpected source IP addresses.

Compensating Controls: Deploy a Web Application Firewall or an Ingress controller with integrated authentication (such as OIDC or OAuth2 proxy) to gate access to the Argo Rollouts dashboard.

Public Exploit Available: No (Exploit available: unknown)

This vulnerability is severe and requires immediate attention to prevent unauthorized control over deployment lifecycles. Security teams should prioritize patching the Argo Rollouts instance and verify that the dashboard is not exposed to public or untrusted networks as a baseline security requirement.