Security readout for executives and security teams
Plain-English summary
A person with physical access to a realme GT 2 may be able to view sensitive information through the “Show app only” setting. The reported impact is disclosure only; no data modification or service disruption is identified. Business risk depends on whether affected phones hold confidential information and are accessible to untrusted people.
Executive priority
Treat as a targeted device-security issue, not an enterprise-wide emergency. Prioritize identification and protection of matching phones used for privileged, regulated, or confidential work. Escalate lost or shared affected devices. Broader emergency action is not supported without evidence of additional affected versions or active exploitation.
Technical view
CVE-2025-25370 is a CWE-200 information-exposure issue reported on realme GT 2 RMX3311 running Android 14 with realme UI 5.0. CVSS 3.1 is 4.6: physical access, low complexity, no privileges, and no user interaction, with high confidentiality impact but no integrity or availability impact.
Likely exposure
Exposure is most credible for realme GT 2 RMX3311 devices running Android 14 with realme UI 5.0. The supplied record does not establish whether other models, builds, or versions are affected. Risk rises for lost, shared, serviced, or weakly controlled devices containing sensitive business data.
Exploitation context
The issue requires physical proximity, substantially limiting remote attack risk. The source bundle does not report inclusion in CISA KEV or evidence of active exploitation. A public research reference exists, but that alone does not establish attacks in the wild.
Researcher notes
The record identifies a physical, low-complexity confidentiality flaw but provides limited affected-version and remediation detail. No CPEs, fixed builds, patches, or vendor advisory are supplied. Testing should remain authorized and focus on confirming unintended disclosure boundaries without collecting unnecessary personal or business data.
Mitigation direction
- Inventory realme GT 2 RMX3311 devices and record Android, realme UI, build, and security patch levels.
- Check realme guidance and device update channels for a confirmed fix or mitigation.
- Restrict physical access to affected devices and strengthen lost-device handling procedures.
- Avoid the “Show app only” function until vendor guidance clarifies safe use.
- Minimize sensitive data stored on devices that cannot be updated or otherwise protected.
Validation and detection
- Confirm whether any managed devices match RMX3311, Android 14, and realme UI 5.0.
- Review installed build and security patch levels against current realme guidance.
- In an authorized controlled setting, verify whether “Show app only” reveals information beyond intended boundaries.
- Revalidate behavior after applying any vendor-provided update or configuration mitigation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-25370 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N0.93.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
4.6MediumVector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://gist.github.com/krl5/4eeed04a065287489c2e606e6d48c1bcCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.