{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-21123 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21123 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21123 is a medium-severity vulnerability in Samsung Mobile Devices, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21123 and fix it if it is affected.\n\nWhat it is: CVE-2026-21123 is a medium-severity vulnerability in Samsung Mobile Devices, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-21123 in the wild and no public exploit code.\n\nAffected product: Samsung Mobile Devices. 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-21123/ (Markdown: https://insights.sbomify.com/CVE-2026-21123/index.md)","id":"CVE-2026-21123","markdown":"https://insights.sbomify.com/CVE-2026-21123/index.md","name":"CVE-2026-21123","record":{"aliases":["GHSA-qmqp-2578-gvhp"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung mobile OS","requires_auth":"high_privilege","summary":"Local attackers with root privileges can access tied profile data before first unlock due to improper privilege management in Samsung mobile devices.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Improper privilege management in Locksettings prior to SMR Oct-2026 Release 1 allows local privileged attackers with root privilege to access data of the tied profile in before first unlock.","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 Samsung Mobile Devices","id":"CVE-2026-21123","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":"Code injection in Samsung Mobile Devices","id":"CVE-2026-21124"},"packages":[],"prev":{"headline":"Memory corruption in Samsung Mobile Devices","id":"CVE-2026-21122"},"products":["Samsung Mobile Devices"],"published":"2026-10-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":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Samsung Mobile"]},"summary":"Local attackers with root privileges can access tied profile data before first unlock due to improper privilege management in Samsung mobile devices.","url":"https://insights.sbomify.com/CVE-2026-21123/"}