{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-27839 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27839 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27839 is a low-severity vulnerability in Tangem SDK, published on 7 Mar 2025. 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-2025-27839 and fix it if it is affected.\n\nWhat it is: CVE-2025-27839 is a low-severity vulnerability in Tangem SDK, published on 7 Mar 2025. 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-2025-27839 in the wild and no public exploit code.\n\nAffected product: Tangem SDK. 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-27839/ (Markdown: https://insights.sbomify.com/CVE-2025-27839/index.md)","id":"CVE-2025-27839","markdown":"https://insights.sbomify.com/CVE-2025-27839/index.md","name":"CVE-2025-27839","record":{"aliases":["GHSA-jmqj-768c-pw4r"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tangem Android SDK","requires_auth":"none","summary":"A logic flaw in the Tangem Android SDK may allow bypassing offline wallet attestation checks during the first card scan, potentially undermining genuineness verification.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1025","name":"Comparison Using Wrong Factors"}],"description":"operations/attestation/AttestationTask.kt in the Tangem SDK before 5.18.3 for Android has a logic flow in offline wallet attestation (genuineness check) that causes verification results to be disregarded during the first scan of a card. Exploitation may not have been possible.","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":"Business logic in SDK","id":"CVE-2025-27839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Security feature bypass in ESP32","id":"CVE-2025-27840"},"packages":[],"prev":{"headline":"An issue was discovered in Artifex Ghostscript before 10.05.0.","id":"CVE-2025-27837"},"products":["SDK"],"published":"2025-03-07","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":"2025-03-10","vendors":["Tangem"]},"summary":"A logic flaw in the Tangem Android SDK may allow bypassing offline wallet attestation checks during the first card scan, potentially undermining genuineness verification.","url":"https://insights.sbomify.com/CVE-2025-27839/"}