{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-21056 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-21056 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21056 is a medium-severity missing authorization vulnerability in Samsung Health, published on 10 Jul 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-21056 and fix it if it is affected.\n\nWhat it is: CVE-2026-21056 is a medium-severity missing authorization vulnerability in Samsung Health, published on 10 Jul 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-21056 in the wild and no public exploit code.\n\nAffected product: Samsung Health. 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-21056/ (Markdown: https://insights.sbomify.com/CVE-2026-21056/index.md)","id":"CVE-2026-21056","markdown":"https://insights.sbomify.com/CVE-2026-21056/index.md","name":"CVE-2026-21056","record":{"aliases":["GHSA-2qcr-4rxg-q25w"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Samsung Health app","requires_auth":"low_privilege","summary":"Local attackers can access connected device information due to improper authorization in Samsung Health.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SamsungMobile","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[],"description":"Improper authorization in Samsung Health prior to version 7.00.0.107 allows local attackers to access connected device information.","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 Health","id":"CVE-2026-21056","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Samsung Pass","id":"CVE-2026-21057"},"packages":[],"prev":{"headline":"Missing authorization in Bixby","id":"CVE-2026-21055"},"products":["Samsung Health"],"published":"2026-07-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["Samsung Mobile"]},"summary":"Local attackers can access connected device information due to improper authorization in Samsung Health.","url":"https://insights.sbomify.com/CVE-2026-21056/"}