Description
Radius is a cloud-native, portable application platform that makes app development easier for teams building cloud-native apps. Prior to 0.58.0, the Kubernetes controller deserializes the user-controlled radapp.io/status annotation on a Deployment and uses its container resource identifier for deletion without confirming ownership by that Deployment. An attacker with permission to modify Deployment annotations and knowledge of a target Radius resource ID can forge radapp.io/status and set radapp.io/enabled to false, causing reconciliation to enter the privileged deletion path for another tenant's Radius-managed container resource. In a multi-tenant installation this confused-deputy condition can delete another team's recoverable container resource and disrupt service; in a single-tenant installation the impact is limited to self denial of service. The multi-tenant Radius controller reads the annotations in pkg/controller/reconciler/annotations.go and reaches the privileged delete in pkg/controller/reconciler/deployment_reconciler.go. The issue does not disclose data, grant privileges, or provide persistence. This issue is fixed in version 0.58.0.
Published: 2026-10-14
Score: 7.7 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized deletion of container resources
Action: Immediate Patch
AI Analysis

Impact

Radius is a cloud‑native application platform that uses a Kubernetes controller to manage container resources. Before version 0.58.0 the controller deserializes the radapp.io/status annotation on a Deployment and deletes the container identified by the annotation without verifying ownership, allowing an attacker who can write Deployment annotations to point the deletion at a different tenant’s resource. This can lead to the removal of a recoverable container, disrupting service for the affected tenant or, in a single‑tenant installation, causing a self deni­al of service.

Affected Systems

The vulnerability affects all releases of the radius‑project product before 0.58.0 that deploy the Kubernetes controller. Users running the radius controller in a multi‑tenant environment are at risk when the controller is enabled, while single‑tenant users are only at risk of self‑induced denial of service. The issue has been fixed in version 0.58.0; no other vendor or product is affected.

Risk and Exploitability

The CVSS score of 7.7 reflects a high severity, but no EPSS score is presently available and the vulnerability is not covered in the CISA KEV catalog. Successful exploitation requires write access to Deployment annotations and knowledge of a target container ID, typically privileges that are restricted to administrators or tenant owners. In a multi‑tenant deployment, the attacker could delete another tenant’s recoverable container, producing a disruptive denial of service; in a single‑tenant environment the impact is limited to service interruption for the affected tenant.

Generated by OpenCVE AI on October 15, 2026 at 13:45 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade radius-project to version 0.58.0 or later to apply the fix
  • Restrict Deployment annotation modification rights by tightening RBAC rules, allowing only trusted service accounts or administrators to modify radapp.io/status
  • If an immediate upgrade is not possible, disable or monitor radapp.io/status updates from untrusted sources to prevent unauthorized deletion
  • Establish alerts for container resource deletions to detect potential abuse

Generated by OpenCVE AI on October 15, 2026 at 13:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-fp5j-4fj2-4jvq Radius Controller May Delete a Container Resource via an Injected Deployment Annotation (Multi-Tenant Installs)
History

Wed, 14 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 14 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
Description Radius is a cloud-native, portable application platform that makes app development easier for teams building cloud-native apps. Prior to 0.58.0, the Kubernetes controller deserializes the user-controlled radapp.io/status annotation on a Deployment and uses its container resource identifier for deletion without confirming ownership by that Deployment. An attacker with permission to modify Deployment annotations and knowledge of a target Radius resource ID can forge radapp.io/status and set radapp.io/enabled to false, causing reconciliation to enter the privileged deletion path for another tenant's Radius-managed container resource. In a multi-tenant installation this confused-deputy condition can delete another team's recoverable container resource and disrupt service; in a single-tenant installation the impact is limited to self denial of service. The multi-tenant Radius controller reads the annotations in pkg/controller/reconciler/annotations.go and reaches the privileged delete in pkg/controller/reconciler/deployment_reconciler.go. The issue does not disclose data, grant privileges, or provide persistence. This issue is fixed in version 0.58.0.
Title Radius Controller May Delete a Container Resource via an Injected Deployment Annotation (Multi-Tenant Installs)
Weaknesses CWE-20
CWE-441
References
Metrics cvssV3_1

{'score': 7.7, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-14T19:42:38.965Z

Reserved: 2026-06-11T16:34:11.635Z

Link: CVE-2026-53999

cve-icon Vulnrichment

Updated: 2026-10-14T19:42:34.559Z

cve-icon NVD

Status : Deferred

Published: 2026-10-14T19:17:17.340

Modified: 2026-10-16T20:04:29.760

Link: CVE-2026-53999

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-15T14:00:07Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-441

    Unintended Proxy or Intermediary ('Confused Deputy')