{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-93540 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-93540 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-93540 is a medium-severity vulnerability in SUSE Rancher, published on 28 Sep 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-93540 and fix it if it is affected.\n\nWhat it is: CVE-2026-93540 is a medium-severity vulnerability in SUSE Rancher, published on 28 Sep 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-93540 in the wild and no public exploit code.\n\nAffected product: SUSE Rancher. 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-93540/ (Markdown: https://insights.sbomify.com/CVE-2026-93540/index.md)","id":"CVE-2026-93540","markdown":"https://insights.sbomify.com/CVE-2026-93540/index.md","name":"CVE-2026-93540","record":{"aliases":["GHSA-m93g-8438-2cgg"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes fleet manager","requires_auth":"low_privilege","summary":"Attackers can modify namespace labels and annotations without proper authorization, bypassing service account restrictions in SUSE Rancher Fleet.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[{"product":"rancher_fleet","vendor":"suse"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A privilege mismatch was found in Fleet. When a bundle requested namespace labels or annotations through the namespaceLabels and namespaceAnnotations options, the resulting namespace metadata update was not subject to the same authorization as the rest of the bundle's deployment. As a result, a bundle could change labels and annotations on a target namespace even when the identity it was pinned to was not authorized to modify that namespace.\n\nThis affected SUSE Rancher Fleet 0.16 before 0.16.2, 0.15 before 0.15.7, 0.14 before 0.14.11, 0.13 before 0.13.16 and potentially older versions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Fleet applies namespace labels and annotations without the bundle's service account privileges","id":"CVE-2026-93540","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Out-of-bounds read in libXi's XQueryDeviceState()","id":"CVE-2026-93541"},"packages":[],"prev":{"headline":"Unauthenticated GitRepo Spec Mutation via Fleet Git Webhook Receiver","id":"CVE-2026-93539"},"products":["Rancher"],"published":"2026-09-28","related":[{"cvss_score":9.9,"headline":"Rancher Fleet vulnerable to cross namespace secret disclosure via unvalidated `valuesFrom` references in Helm Deployer","id":"CVE-2026-44935","kev_date_added":null,"published":"2026-07-02"},{"cvss_score":9.9,"headline":"Helm impersonation bypass of `RESTClientGetter` retains `cluster-admin` during template rendering","id":"CVE-2026-41050","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":8.8,"headline":"Privilege escalation in Rancher","id":"CVE-2026-88808","kev_date_added":null,"published":"2026-09-28"},{"cvss_score":8.8,"headline":"Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent","id":"CVE-2026-44938","kev_date_added":null,"published":"2026-07-07"},{"cvss_score":8.3,"headline":"SUSE Rancher Fleet had an Unauthenticated Webhook: Regex Injection via Unsanitized Repository URL Components","id":"CVE-2026-44937","kev_date_added":null,"published":"2026-07-06"},{"cvss_score":7.1,"headline":"Missing authorization in Rancher","id":"CVE-2026-93538","kev_date_added":null,"published":"2026-09-28"},{"cvss_score":6.5,"headline":"Path traversal in Fleet Helm valuesFiles allows disclosure of files outside the bundle directory","id":"CVE-2026-93537","kev_date_added":null,"published":"2026-09-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2026-09-28","vendors":["SUSE"]},"summary":"Attackers can modify namespace labels and annotations without proper authorization, bypassing service account restrictions in SUSE Rancher Fleet.","url":"https://insights.sbomify.com/CVE-2026-93540/"}