CVE-2026-53999

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-06-12. A secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-101606 (ENISA EUVD) · GHSA-fp5j-4fj2-4jvq (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 12, 2026

Last Modified

October 16, 2026

Advisory Details (4)

Auto-updated Oct 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

Radius v0.58.0

Patch available: radius-project/radius v0.58.0

https://github.com/radius-project/radius/releases/tag/v0.58.0
GitHub commit

commit c4174fc205b8 (radius-project/radius)

Fix landed in radius-project/radius commit c4174fc205b8 — awaiting tagged release

https://github.com/radius-project/radius/commit/c4174fc205b838d5eab4f64b4909001ab08c0587
GitHub pull request

fix: tenant validation

Fix merged in radius-project/radius PR #11967 on 2026-05-21 — awaiting tagged release

https://github.com/radius-project/radius/pull/11967
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Radius Controller May Delete a Container Resource via an Injected Deployment Annotation (Multi-Tenant Installs) · Advisory · radius-project/radius · GitHub

https://github.com/radius-project/radius/security/advisories/GHSA-fp5j-4fj2-4jvq

Vendor Advisories for CVE-2026-53999(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/radius-project/radius @ 0.58.0 (fixes < 0.58.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/radius-project/radius—
  • every version up to 0.58.0: fixed in 0.58.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-01 07:45 UTCGHSA enrichmentGHSA-fp5j-4fj2-4jvq · GitHub severity HIGH · GitHub CVSS 7.7
  3. 2026-11-01 07:45 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-10-30 19:44 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-10-25 14:20 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-23 20:00 UTCEG score recompute
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  21. 2026-10-18 03:31 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-16 20:09 UTCEG score recompute
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
Show 13 more
  1. 2026-10-14 20:27 UTCEG score recompute
  2. 2026-10-14 19:55 UTCEG score recompute
  3. 2026-10-14 19:33 UTCEG score recompute
  4. 2026-10-12 15:57 UTCEG score recompute
  5. 2026-10-11 19:40 UTCEG score recompute
  6. 2026-10-11 16:55 UTCEG score recompute
  7. 2026-10-11 14:18 UTCEG score recompute
  8. 2026-07-31 00:23 UTCEG score recompute
  9. 2026-07-26 20:32 UTCEG score recompute
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 16th percentile
  12. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 16th percentile
  13. 2026-06-12 20:11 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53999?
CVE-2026-53999 is a high-severity vulnerability; its CVE record was published on June 12, 2026. 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…
When was the CVE record for CVE-2026-53999 published?
The CVE record for CVE-2026-53999 was published on June 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-53999 actively exploited?
CVE-2026-53999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53999?
CVE-2026-53999 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53999?
A fix for CVE-2026-53999 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53999 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53999

Explore →

Is Your Infrastructure Affected by CVE-2026-53999?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs