{"answers":{"affected":"3 open source packages ship an affected version, including github.com/kcp-dev/kcp.","exploited":"There is no known exploitation of CVE-2025-29922 in the wild and no public exploit code.","fix":"Upgrade github.com/kcp-dev/kcp to 0.26.3 or later.","what":"CVE-2025-29922 is a critical missing authorization vulnerability in kcp-dev kcp, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-29922 and fix it if it is affected.\n\nWhat it is: CVE-2025-29922 is a critical missing authorization vulnerability in kcp-dev kcp, published on 20 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-29922 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/kcp-dev/kcp (Go): affected all versions; fixed in 0.26.3\n- github.com/kcp-dev/kcp (Go): affected all versions; fixed in 0.26.3\n- github.com/kcp-dev/kcp (Go): affected all versions; fixed in 0.26.3\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-29922/ (Markdown: https://insights.sbomify.com/CVE-2025-29922/index.md)","id":"CVE-2025-29922","markdown":"https://insights.sbomify.com/CVE-2025-29922/index.md","name":"CVE-2025-29922","record":{"aliases":["GHSA-w2rr-38wv-8rrp","GO-2025-3538"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes control plane","requires_auth":"low_privilege","summary":"Attackers can create or delete objects in arbitrary workspaces without proper authorization, bypassing APIBinding requirements in kcp control planes.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.6,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"kcp is a Kubernetes-like control plane for form-factors and use-cases beyond Kubernetes and container workloads. Prior to 0.26.3, the identified vulnerability allows creating or deleting an object via the APIExport VirtualWorkspace in any arbitrary target workspace for pre-existing resources. By design, this should only be allowed when the workspace owner decides to give access to an API provider by creating an APIBinding. With this vulnerability, it is possible for an attacker to create and delete objects even if none of these requirements are satisfied, i.e. even if there is no APIBinding in that workspace at all or the workspace owner has created an APIBinding, but rejected a permission claim. A fix for this issue has been identified and has been published with kcp 0.26.3 and 0.27.0.","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":"kcp allows unauthorized creation and deletion of objects in arbitrary workspaces through APIExport Virtual Workspace","id":"CVE-2025-29922","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"go-redis allows potential out of order responses when `CLIENT SETINFO` times out during connection establishment","id":"CVE-2025-29923"},"packages":[{"ecosystem":"Go","fixed":["0.26.3"],"introduced":["0"],"last_affected":[],"package":"github.com/kcp-dev/kcp","purl":null,"source":"GHSA-w2rr-38wv-8rrp"},{"ecosystem":"Go","fixed":["0.26.3"],"introduced":["0"],"last_affected":[],"package":"github.com/kcp-dev/kcp","purl":"pkg:golang/github.com/kcp-dev/kcp","source":"GHSA-w2rr-38wv-8rrp"},{"ecosystem":"Go","fixed":["0.26.3"],"introduced":["0"],"last_affected":[],"package":"github.com/kcp-dev/kcp","purl":"pkg:golang/github.com/kcp-dev/kcp","source":"GO-2025-3538"}],"prev":{"headline":"Suricata pcre: negated pcr can cause infinite loop","id":"CVE-2025-29918"},"products":["kcp"],"published":"2025-03-20","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":"total"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["kcp-dev"]},"summary":"Attackers can create or delete objects in arbitrary workspaces without proper authorization, bypassing APIBinding requirements in kcp control planes.","url":"https://insights.sbomify.com/CVE-2025-29922/"}