Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82277 – Unauthenticated Rollout Manipulation (RCE-adjacent Deployment Hijack) – Argo Rollou

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82277 is a missing authentication vulnerability (CWE-306) affecting the built-in dashboard of Argo Rollouts, the Kubernetes progressive delivery controller. The dashboard binds to all network interfaces and exposes multiple state-changing Rollout operations with no authentication, authorization, or CSRF protection, allowing any network-reachable attacker to manipulate application deployments. The flaw carries a Critical severity rating (CVSS v3.1 9.8 / CVSS v4.0 9.3).

Technical details

  • Root cause: the Argo Rollouts dashboard binds to all network interfaces (not restricted to localhost) and does not enforce authentication, authorization, or CSRF protection on mutating API calls.
  • Trigger condition: any client with network access to the dashboard port can send unauthenticated requests to invoke Rollout operations.
  • Attack vector: network, no privileges and no user interaction required.
  • Exposed operations: PromoteRollout, AbortRollout, RestartRollout, SetRolloutImage, UndoRollout, and RetryRollout.
  • Impact: an attacker can promote, abort, restart, retry, or roll back Rollouts and change the deployed container image, across every namespace accessible to the Argo Rollouts controller’s kubeconfig — effectively giving full control over affected application deployments and enabling deployment of attacker-chosen images.

Affected software

  • argoproj/argo-rollouts dashboard, versions 0 through 1.10.0 (semver)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade to a fixed release of Argo Rollouts once the vendor publishes one; monitor the argoproj/argo-rollouts repository and security advisories for the patched version number, as it was not confirmed at time of writing.
  • If no patch is yet available:
    • Do not expose the Argo Rollouts dashboard directly to untrusted networks; bind it to localhost or restrict it behind a reverse proxy/service mesh enforcing authentication.
    • Restrict access at the network layer (firewall rules, Kubernetes NetworkPolicy, VPN-only access) so only trusted operators can reach the dashboard port.
    • Disable the dashboard where it is not actively required.
    • Audit Rollout objects and controller kubeconfig permissions to limit the blast radius of any unauthorized mutation.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: Argo Rollouts

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge