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

> An attacker can delete another tenant's container resources by forging deployment annotations in multi-tenant Radius installations, causing service disruption.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-fp5j-4fj2-4jvq, GO-2026-5373

## What is CVE-2026-53999?

CVE-2026-53999 is a high-severity vulnerability in radius-project radius, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-441 (Unintended Proxy or Intermediary), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-53999?

3 open source packages ship an affected version, including github.com/radius-project/radius.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/radius-project/radius` | Go | All versions | 0.58.0 |
| `github.com/radius-project/radius` | Go | All versions | 0.58.0 |
| `github.com/radius-project/radius` | Go | All versions | 0.58.0 |

## How do I fix CVE-2026-53999?

Upgrade github.com/radius-project/radius to 0.58.0 or later.

## Is CVE-2026-53999 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53999 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53999 and fix it if it is affected.

What it is: CVE-2026-53999 is a high-severity vulnerability in radius-project radius, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53999 exists.

Affected packages and fixed versions:
- github.com/radius-project/radius (Go): affected all versions; fixed in 0.58.0
- github.com/radius-project/radius (Go): affected all versions; fixed in 0.58.0
- github.com/radius-project/radius (Go): affected all versions; fixed in 0.58.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53999/ (Markdown: https://insights.sbomify.com/CVE-2026-53999/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53999
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53999
- OSV: https://osv.dev/vulnerability/CVE-2026-53999

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53999/
Summaries are generated and may contain mistakes; the official description above is the record.