{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-21076 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-21076 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-21076 is a medium-severity missing authorization vulnerability in Samsung Account, published on 5 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-21076 and fix it if it is affected.\n\nWhat it is: CVE-2025-21076 is a medium-severity missing authorization vulnerability in Samsung Account, published on 5 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-21076 in the wild and no public exploit code.\n\nAffected product: Samsung Account. 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-2025-21076/ (Markdown: https://insights.sbomify.com/CVE-2025-21076/index.md)","id":"CVE-2025-21076","markdown":"https://insights.sbomify.com/CVE-2025-21076/index.md","name":"CVE-2025-21076","record":{"aliases":["GHSA-vm9p-cjxm-7x59"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Account app","requires_auth":"none","summary":"Local attackers can access Samsung Account data due to improper permission handling, requiring user interaction to trigger.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[{"product":"account","vendor":"samsung"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Improper handling of insufficient permissions or privileges in Samsung Account prior to version 15.5.00.18 allows local attackers to access data in Samsung Account. User interaction is required for triggering this vulnerability.","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":"Missing authorization in Samsung Account","id":"CVE-2025-21076","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Samsung Email","id":"CVE-2025-21077"},"packages":[],"prev":{"headline":"Memory corruption in Samsung Mobile Devices","id":"CVE-2025-21075"},"products":["Samsung Account"],"published":"2025-11-05","related":[{"cvss_score":6.9,"headline":"Open redirect in Samsung Account","id":"CVE-2026-20994","kev_date_added":null,"published":"2026-03-16"},{"cvss_score":5.9,"headline":"Privilege escalation in Samsung Account","id":"CVE-2022-30735","kev_date_added":null,"published":"2022-06-07"},{"cvss_score":5.5,"headline":"Information disclosure in Samsung Account","id":"CVE-2023-42546","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":5.5,"headline":"Information disclosure in Samsung Account","id":"CVE-2023-42547","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":5.5,"headline":"Other in Samsung Account","id":"CVE-2023-42548","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":5.5,"headline":"Information disclosure in Samsung Account","id":"CVE-2023-42549","kev_date_added":null,"published":"2023-11-07"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-07","vendors":["Samsung Mobile"]},"summary":"Local attackers can access Samsung Account data due to improper permission handling, requiring user interaction to trigger.","url":"https://insights.sbomify.com/CVE-2025-21076/"}