{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-71403 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-71403 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-71403 is a medium-severity authentication bypass vulnerability in SUSE Rancher, published on 3 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-71403 and fix it if it is affected.\n\nWhat it is: CVE-2026-71403 is a medium-severity authentication bypass vulnerability in SUSE Rancher, published on 3 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-71403 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-71403/ (Markdown: https://insights.sbomify.com/CVE-2026-71403/index.md)","id":"CVE-2026-71403","markdown":"https://insights.sbomify.com/CVE-2026-71403/index.md","name":"CVE-2026-71403","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Rancher management platform","requires_auth":"high_privilege","summary":"Attackers with update permissions can hijack accounts by rebinding identity principals, leading to unauthorized access and privilege escalation in Rancher.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[{"product":"rancher","vendor":"suse"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"A flaw was found in Rancher Manager. The /v3/users update path did not enforce immutability of a User resource's `username` and `principalIds` fields. A user holding the `update` verb on `users.management.cattle.io` could inject a foreign identity provider principal into any account, so that the next login by the owner of that principal was bound to the victim's account and inherited its role bindings.\n\nThis issue affects Rancher: before 2.15.1.","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":"Rancher: Identity-field mutation in /v3/users allows account hijack via principal rebind","id":"CVE-2026-71403","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Rancher: Ownership-less ClusterRole overwrite via attacker-controlled cr-name annotation on GlobalRole","id":"CVE-2026-71404"},"packages":[],"prev":{"headline":"wicked: out-of-bounds read in the DHCPv4 option parser due to payload length taken from the IP total length","id":"CVE-2026-71402"},"products":["Rancher"],"published":"2026-09-03","related":[{"cvss_score":9.9,"headline":"Rancher vulnerable to Privilege Escalation via manipulation of Secrets","id":"CVE-2023-22647","kev_date_added":null,"published":"2023-06-01"},{"cvss_score":9.9,"headline":"Rancher Webhook is misconfigured during upgrade process","id":"CVE-2023-22651","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.9,"headline":"Rancher: Exposure of sensitive fields","id":"CVE-2022-43757","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":9.9,"headline":"Rancher: Plaintext storage and exposure of credentials in Rancher API and cluster.management.cattle.io object","id":"CVE-2021-36782","kev_date_added":null,"published":"2022-09-07"},{"cvss_score":9.9,"headline":"Rancher: Failure to properly sanitize credentials in cluster template answers","id":"CVE-2021-36783","kev_date_added":null,"published":"2022-09-07"},{"cvss_score":9.8,"headline":"Rancher Recreates Default User With Known Password Despite Deletion","id":"CVE-2019-11202","kev_date_added":null,"published":"2019-07-30"},{"cvss_score":9.5,"headline":"SAML Authentication Replay in Rancher","id":"CVE-2026-44946","kev_date_added":null,"published":"2026-06-30"}],"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":"total"},"state":"PUBLISHED","updated":"2026-09-04","vendors":["SUSE"]},"summary":"Attackers with update permissions can hijack accounts by rebinding identity principals, leading to unauthorized access and privilege escalation in Rancher.","url":"https://insights.sbomify.com/CVE-2026-71403/"}