Cloud Vulnerability DB
An open project to list all known cloud vulnerabilities and Cloud Service Provider security issues
Vulnerability DatabaseCVE-2025-48710
CVE-2025-48710:
vulnerability analysis and mitigation
Overview
kro (Kube Resource Orchestrator) version 0.1.0 before 0.2.1 contains a confused deputy vulnerability (CVE-2025-48710) that allows users with permission to create or modify ResourceGraphDefinition resources to supply arbitrary container images. The vulnerability was discovered in June 2025 and affects the core functionality of kro, an alpha experimental open-source project maintained by AWS, Google Cloud and Azure (Orca Blog).
Technical details
The vulnerability stems from kro's handling of CustomResourceDefinitions (CRDs) and ResourceGraphDefinition resources. The issue occurs because kro doesn't actively watch for CRD modifications, and auto-scheduled reconciliation is only triggered based on the resync period, which is every 10 hours by default. This allows attackers to confuse kro's microcontroller by directly modifying its watched CRD, regardless of modifying the original ResourceGraphDefinition resource. The vulnerability has been assigned a CVSS v3.1 score of 4.1 MEDIUM (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N) (NVD).
Impact
Successful exploitation of this vulnerability can lead to a confused-deputy scenario where kro's controllers deploy and run attacker-controlled images, resulting in unauthenticated remote code execution on cluster nodes. Attackers can replace default images with malicious ones, potentially achieving remote code execution within containers in the cluster (Orca Blog).
Mitigation and workarounds
The vulnerability has been patched in versions 0.2.1 and later. No user intervention is required beyond updating to the fixed version. The fix addresses the issue of CRD modifications and improves the handling of dynamic informers (GitHub Patch).
Community reactions
The kro maintainers responded promptly to the vulnerability report by immediately opening a related issue and working on a fix. However, they noted that kro considers the ability to mutate a CRD a cluster-admin permission and not a vulnerability in kro itself. The project is currently in alpha experimental stage and not intended for production use (Orca Blog).
Additional resources
Source: This report was generated using AI
Free Vulnerability Assessment
Benchmark your Cloud Security Posture
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
Ready to see Wiz in action?
“Best User Experience I have ever seen, provides full visibility to cloud workloads.”
David EstlickCISO
“Wiz provides a single pane of glass to see what is going on in our cloud environments.”
Adam FletcherChief Security Officer
“We know that if Wiz identifies something as critical, it actually is.”
Greg PoniatowskiHead of Threat and Vulnerability Management