{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-25370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25370 is a medium-severity vulnerability in n/a, published on 14 May 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-25370 and fix it if it is affected.\n\nWhat it is: CVE-2025-25370 is a medium-severity vulnerability in n/a, published on 14 May 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-25370 in the wild and no public exploit code.\n\nAffected product: n/a. 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-25370/ (Markdown: https://insights.sbomify.com/CVE-2025-25370/index.md)","id":"CVE-2025-25370","markdown":"https://insights.sbomify.com/CVE-2025-25370/index.md","name":"CVE-2025-25370","record":{"aliases":["GHSA-m7cj-8qx5-j738"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"realme GT 2","requires_auth":"none","summary":"A physically proximate attacker can obtain sensitive information from realme GT 2 devices via the show app only setting function.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue in realme GT 2 (RMX3311) running Android 14 with realme UI 5.0 allows a physically proximate attacker to obtain sensitive information via the show app only setting function.","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":"Information disclosure in n/a","id":"CVE-2025-25370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2025-25371"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-25364"},"products":["n/a"],"published":"2025-05-14","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-07-27","vendors":["n/a"]},"summary":"A physically proximate attacker can obtain sensitive information from realme GT 2 devices via the show app only setting function.","url":"https://insights.sbomify.com/CVE-2025-25370/"}