Ad · Leaderboard 728×90

CVE-2026-53999

7.7High

Published 14 Oct 2026 · NVD status: Deferred · AI triage by gemini-3.8-flash

7.7High
Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None
Impact
High impact on availability
Weakness
CWE-20, CWE-441

Impact

Authenticated attackers with Deployment edit permissions can trigger the Radius controller to delete another tenant's container resources. They need write access to Deployment annotations and knowledge of the target resource ID.

Root cause

The controller deletes container resources specified in the user-controlled 'radapp.io/status' annotation without verifying resource ownership.

Affected systems

Radius prior to 0.58.0

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

Fix & remediation

Upgrade Radius to 0.58.0 or newer. If patching cannot happen immediately, restrict Kubernetes RBAC permissions so untrusted tenants cannot modify Deployment annotations.

shell
$ rad install kubernetes --version 0.58.0

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-53999

Ad · Sticky 320×50 / 728×90