{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-10090 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-10090 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-10090 is a critical vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-10090 and fix it if it is affected.\n\nWhat it is: CVE-2026-10090 is a critical vulnerability in Red Hat Advanced Cluster Management for Kubernetes 2.11, published on 5 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-10090 in the wild and no public exploit code.\n\nAffected product: Red Hat Advanced Cluster Management for Kubernetes 2.11. 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-10090/ (Markdown: https://insights.sbomify.com/CVE-2026-10090/index.md)","id":"CVE-2026-10090","markdown":"https://insights.sbomify.com/CVE-2026-10090/index.md","name":"CVE-2026-10090","record":{"aliases":["GHSA-g9vp-wj77-5767"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes cluster management","requires_auth":"high_privilege","summary":"Namespace edit users can escalate to cluster-admin by deploying malicious Helm charts via Application Subscription due to missing authorization checks.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-267","name":"Privilege Defined With Unsafe Actions"}],"description":"A flaw was found in the Application Subscription controller (multicluster-operators-subscription) of Red Hat Advanced Cluster Management for Kubernetes (ACM). A user with namespace-scoped \"edit\" privileges in an ACM hub namespace can create a Channel resource pointing to a Helm repository they control and a Subscription resource referencing it. The app-subscription controller fetches and applies the Helm chart contents with its own elevated authority, without verifying whether the subscription creator holds the \"open-cluster-management:subscription-admin\" role and without restricting applied resources to the subscription namespace. This allows the attacker to include cluster-scoped resources in the Helm chart, such as a ClusterRoleBinding granting the attacker's ServiceAccount the \"cluster-admin\" ClusterRole. Successful exploitation results in full cluster-admin privilege escalation. This contradicts the ACM documentation which states that non-subscription-admin users should have resources deployed into the subscription namespace only.","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":"Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2.11","id":"CVE-2026-10090","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Email JavaScript Cloak \u003c= 1.03 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2026-10091"},"packages":[],"prev":{"headline":"Insert Pages \u003c= 3.11.4 - Authenticated (Author+) Stored Cross-Site Scripting via Custom Field Keys (Meta Key Names)","id":"CVE-2026-10089"},"products":["Red Hat Advanced Cluster Management for Kubernetes 2.11","Red Hat Advanced Cluster Management for Kubernetes 2.13","Red Hat Advanced Cluster Management for Kubernetes 2.14","Red Hat Advanced Cluster Management for Kubernetes 2.15","Red Hat Advanced Cluster Management for Kubernetes 2.16","Red Hat Advanced Cluster Management for Kubernetes 2.17"],"published":"2026-08-05","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-08","vendors":["Red Hat"]},"summary":"Namespace edit users can escalate to cluster-admin by deploying malicious Helm charts via Application Subscription due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2026-10090/"}