{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-73268 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-73268 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-73268 is a critical code injection vulnerability in Red Hat multicluster engine for Kubernetes 2.10, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73268 and fix it if it is affected.\n\nWhat it is: CVE-2026-73268 is a critical code injection vulnerability in Red Hat multicluster engine for Kubernetes 2.10, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-73268 in the wild and no public exploit code.\n\nAffected product: Red Hat multicluster engine for Kubernetes 2.10. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2026-73268/ (Markdown: https://insights.sbomify.com/CVE-2026-73268/index.md)","id":"CVE-2026-73268","markdown":"https://insights.sbomify.com/CVE-2026-73268/index.md","name":"CVE-2026-73268","record":{"aliases":["GHSA-6c6p-j4gf-mj2c"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes multicluster engine","requires_auth":"low_privilege","summary":"Attackers with ClusterCurator permissions can inject arbitrary Job specs to execute code and escalate privileges within the Kubernetes cluster.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"A flaw was found in the cluster-curator-controller component of multicluster engine (MCE). A tenant with create or update permissions on ClusterCurator resources can inject an arbitrary Job specification. This is possible because the CreateJob() function does not validate user-controlled input when unmarshaling the spec.install.overrideJob raw extension. Successful exploitation allows the injected Job to run with the controller's elevated privileges, leading to arbitrary code execution and privilege escalation, potentially accessing cluster-wide secrets.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cluster-curator-controller: cluster-curator-controller: spec.install.overridejob allows arbitrary job spec injection","id":"CVE-2026-73268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Privilege escalation in multicluster engine for Kubernetes 2.10","id":"CVE-2026-73269"},"packages":[],"prev":{"headline":"Missing authorization in multicluster engine for Kubernetes 2.10","id":"CVE-2026-73267"},"products":["multicluster engine for Kubernetes 2.10","multicluster engine for Kubernetes 2.11","multicluster engine for Kubernetes 2.17","multicluster engine for Kubernetes 2.6","multicluster engine for Kubernetes 2.8","multicluster engine for Kubernetes 2.9"],"published":"2026-08-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-09-29","vendors":["Red Hat"]},"summary":"Attackers with ClusterCurator permissions can inject arbitrary Job specs to execute code and escalate privileges within the Kubernetes cluster.","url":"https://insights.sbomify.com/CVE-2026-73268/"}