{"answers":{"affected":"3 open source packages ship an affected version, including github.com/kro-run/kro.","exploited":"There is no known exploitation of CVE-2025-48710 in the wild and no public exploit code.","fix":"Upgrade github.com/kro-run/kro to 0.2.1 or later.","what":"CVE-2025-48710 is a medium-severity code injection vulnerability in kro.run kro, published on 4 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48710 and fix it if it is affected.\n\nWhat it is: CVE-2025-48710 is a medium-severity code injection vulnerability in kro.run kro, published on 4 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48710 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/kro-run/kro (Go): affected all versions; fixed in 0.2.1\n- github.com/kro-run/kro (Go): affected from 0.1.0; fixed in 0.2.1\n- github.com/kro-run/kro (Go): affected from 0.1.0; fixed in 0.2.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-48710/ (Markdown: https://insights.sbomify.com/CVE-2025-48710/index.md)","id":"CVE-2025-48710","markdown":"https://insights.sbomify.com/CVE-2025-48710/index.md","name":"CVE-2025-48710","record":{"aliases":["GHSA-7633-x85h-5mqh","GO-2025-3741"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes resource orchestrator","requires_auth":"high_privilege","summary":"Attackers with resource creation permissions can deploy malicious container images, leading to remote code execution on cluster nodes.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-441","name":"Unintended Proxy or Intermediary"}],"description":"kro (Kube Resource Orchestrator) 0.1.0 before 0.2.1 allows users (with permission to create or modify ResourceGraphDefinition resources) to supply arbitrary container images. This 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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"kro Confused Deputy vulnerability","id":"CVE-2025-48710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"QTS, QuTS hero","id":"CVE-2025-48721"},"packages":[{"ecosystem":"Go","fixed":["0.2.1"],"introduced":["0"],"last_affected":[],"package":"github.com/kro-run/kro","purl":"pkg:golang/github.com/kro-run/kro","source":"GO-2025-3741"},{"ecosystem":"Go","fixed":["0.2.1"],"introduced":["0.1.0"],"last_affected":[],"package":"github.com/kro-run/kro","purl":null,"source":"GHSA-7633-x85h-5mqh"},{"ecosystem":"Go","fixed":["0.2.1"],"introduced":["0.1.0"],"last_affected":[],"package":"github.com/kro-run/kro","purl":"pkg:golang/github.com/kro-run/kro","source":"GHSA-7633-x85h-5mqh"}],"prev":{"headline":"BMC Control-M/Server cleartext database credentials in process lists and logs","id":"CVE-2025-48709"},"products":["kro"],"published":"2025-06-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-04","vendors":["kro.run"]},"summary":"Attackers with resource creation permissions can deploy malicious container images, leading to remote code execution on cluster nodes.","url":"https://insights.sbomify.com/CVE-2025-48710/"}