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.
References
Configurations
No configuration.
History
14 Oct 2026, 20:17
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/radius-project/radius/security/advisories/GHSA-fp5j-4fj2-4jvq - |
14 Oct 2026, 19:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-14 19:17
Updated : 2026-10-16 20:04
NVD link : CVE-2026-53999
Mitre link : CVE-2026-53999
CVE.ORG link : CVE-2026-53999
JSON object : View
Products Affected
No product.
