{"answers":{"affected":"It affects 9 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26075 exists.","fix":"Apply the vendor's patch.","what":"CVE-2023-26075 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 10 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26075 and fix it if it is affected.\n\nWhat it is: CVE-2023-26075 is a high-severity memory corruption vulnerability in Samsung Exynos 1080 Firmware, published on 10 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26075 exists.\n\nAffected product: Samsung Exynos 1080 Firmware. 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-2023-26075/ (Markdown: https://insights.sbomify.com/CVE-2023-26075/index.md)","id":"CVE-2023-26075","markdown":"https://insights.sbomify.com/CVE-2023-26075/index.md","name":"CVE-2023-26075","record":{"aliases":["A-269656722","GHSA-fg8g-w97j-ff9c","PUB-A-269656722"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Exynos chipset","requires_auth":"low_privilege","summary":"Attackers can exploit an intra-object overflow in the 5G MM message codec to potentially execute code or escalate privileges on affected Samsung devices.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exynos_1080_firmware","vendor":"samsung"},{"product":"exynos_1280_firmware","vendor":"samsung"},{"product":"exynos_2200_firmware","vendor":"samsung"},{"product":"exynos_850_firmware","vendor":"samsung"},{"product":"exynos_980_firmware","vendor":"samsung"},{"product":"exynos_auto_t5123_firmware","vendor":"samsung"},{"product":"exynos_modem_5123_firmware","vendor":"samsung"},{"product":"exynos_modem_5300_firmware","vendor":"samsung"},{"product":"exynos_w920_firmware","vendor":"samsung"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:N/A:H/C:L/I:L/PR:L/S:U/UI:N","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"An issue was discovered in Samsung Mobile Chipset and Baseband Modem Chipset for Exynos 850, Exynos 980, Exynos 1080, Exynos 1280, Exynos 2200, Exynos Modem 5123, Exynos Modem 5300, and Exynos Auto T5123. An intra-object overflow in the 5G MM message codec can occur due to insufficient parameter validation when decoding the Service Area List.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Memory corruption in n/a","id":"CVE-2023-26075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"samsung:exynos_1080_firmware","products":["samsung:exynos_1080_firmware","samsung:exynos_1280_firmware","samsung:exynos_2200_firmware","samsung:exynos_850_firmware","samsung:exynos_980_firmware","samsung:exynos_modem_5300_firmware","samsung:exynos_w920_firmware"],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":6,"next":{"headline":"Memory corruption in n/a","id":"CVE-2023-26076"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2023-26074"},"products":["n/a"],"published":"2023-03-10","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2025-54328","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-62818","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.1,"headline":"Denial of service in n/a","id":"CVE-2025-58349","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-27807","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-47202","kev_date_added":null,"published":"2025-07-07"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2025-27891","kev_date_added":null,"published":"2025-05-14"},{"cvss_score":8.8,"headline":"Use after free in n/a","id":"CVE-2025-23102","kev_date_added":null,"published":"2025-06-03"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-27","vendors":["n/a"]},"summary":"Attackers can exploit an intra-object overflow in the 5G MM message codec to potentially execute code or escalate privileges on affected Samsung devices.","url":"https://insights.sbomify.com/CVE-2023-26075/"}