Honor Tileservice
CVE-2025-57837
LOW
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local foothold on device
-
ExploitInteract with Tileservice module
-
ExecutionTrigger information leak condition
-
ImpactRead exposed confidential data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access to an affected Honor device (AV:L) and the ability to interact with the Tileservice module, combined with the specific state or timing conditions implied by the high attack complexity (AC:H), which materially limits practical exploitation. The input description does not name an exact configuration setting, protocol, or deployment mode that must be enabled, so the precise trigger condition is not specified in available data and should be confirmed against Honor's advisory. Limiting factors: no network reachability (local only), high complexity, and only low-confidentiality impact with no integrity or availability effect; despite PR:N in the vector, an attacker realistically needs an unprivileged app or shell foothold on the device. |
| Impact | This is a genuinely low-priority issue across nearly every signal, not a high-CVSS flaw masquerading as low risk - the CVSS base score itself is only 2.9 (Low). The CVSS 3.1 vector (AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N) describes a local-only attack (AV:L) with high attack complexity (AC:H), no privileges and no user interaction, yielding only low confidentiality impact and zero integrity or availability impact. EPSS reinforces this: 0.18% probability (6th percentile) indicates very low likelihood of exploitation activity. The CVE is NOT listed in CISA KEV and no public exploit code is referenced, so there is no public exploit identified at time of analysis. There is no SSVC decision data in the input to evaluate automatability or technical impact. The only tension worth noting is that PR:N (no privileges) combined with AV:L is unusual for an on-device Android/vendor-OS module - local attack vectors typically presuppose at least an unprivileged app or shell on the device, so 'no privileges' likely means 'no special app permissions' rather than 'no foothold'; the practical prerequisite of local presence should be verified against Honor's advisory. Overall: a minor information-disclosure weakness, low real-world urgency. |
| Exploit ScenarioDerived | A malicious or compromised application already present on an Honor device, or a user with local shell access, interacts with the Tileservice module under specific timing or state conditions (reflecting the high attack complexity) to read information the module should not expose. No public exploit code is referenced, and the leak yields only limited confidential data rather than code execution or device compromise. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Information disclosure in the Honor Tileservice module allows a local attacker on an affected Honor device to read data that should remain confidential, with exploitation requiring the specific state or timing conditions implied by a high attack-complexity rating. The impact is confined to low confidentiality loss - integrity and availability are unaffected - and the CVSS 3.1 base score of 2.9 places this firmly in the Low severity band, corroborated by a negligible EPSS probability of 0.18% (6th percentile). No public exploit code has been identified at time of analysis, there is no CISA KEV listing, and the Honorable vendor advisory is the authoritative source for the precise affected configurations and fix status. Per the assessed vector (AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N), an attacker needs local access to the device and a foothold such as an unprivileged app or shell despite the PR:N rating.
RemediationAI
Patch status cannot be confirmed from the provided data: no vendor-released patch version is identified in the input, so treat this as no vendor-released patch identified at time of analysis, and obtain the definitive fix and affected-build list from Honor's advisory at https://www.honor.com/global/security/cve-2025-57837/ and from Honor's normal over-the-air security update channel. Where immediate remediation is unavailable, the highest-value compensating control is to reduce the local attack surface: restrict installation to trusted app sources and audit sideloaded or untrusted applications, since exploitation requires a local foothold inside the device (the trade-off is reduced flexibility for developers and power users who rely on sideloading). Device management teams can also tighten app permission policies and monitor for anomalous tile-service interaction, accepting that such monitoring provides detection rather than prevention. Given the Low severity, high attack complexity, and purely local, confidentiality-only impact, emergency mitigations are not warranted; prioritize applying the Honor security update through standard patching cycles.
Affected ProductsAI
The affected component is the Tileservice module on Honor devices; the provided intelligence does not include CPE strings or an explicit product/version matrix, so the exact model and MagicOS build ranges must be taken from Honor's vendor advisory at https://www.honor.com/global/security/cve-2025-57837/. That advisory is the sole reference supplied (NVD-sourced link to Honor's security page) and should be consulted to determine which Honor handsets and firmware builds carry the vulnerable Tileservice implementation. No third-party or downstream products are indicated in the available data, and no additional affected platforms can be confirmed from the supplied references.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Tileservice is a system-level module on Honor devices (MagicOS/Android-based) that manages quick-settings tiles and the service-side handling of tile requests. The weakness class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), meaning the module returns or makes observable data beyond what the caller is entitled to see, rather than corrupting or executing data. The assessed vector CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N indicates the flaw is only reachable with local access (AV:L), that successful exploitation depends on a narrow race, ordering, or state prerequisite (AC:H), and that no privileges are required per the vector (PR:N) and no user interaction is needed (UI:N). Scope is unchanged and the sole impact is low confidentiality loss; there is no integrity or availability effect. Because the available data does not identify the exact configuration setting, IPC interface, or deployment mode that must be enabled, the concrete trigger condition is not specified in the provided intelligence and should be confirmed against Honor's advisory. In practice, a realistic attacker would need an unprivileged app or shell on the device to reach the module, which is consistent with the local-access vector.
Know when Honor gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Local-only on-device module (AV:L) with state/timing-dependent trigger (AC:H); no app permissions needed (PR:N); only partial confidential data exposed (C:L), no integrity or availability impact.
Primary rating from Vendor (3836d913-7555-4dd0-a509-f5667fdf5fe4).
CVSS VectorVendor: 3836d913-7555-4dd0-a509-f5667fdf5fe4
DescriptionCVE.org
Tileservice module is affected by information leak vulnerability, successful exploitation of this vulnerability may affect service confidentiality.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Several services in Honor Device Co., Ltd Honor PC Manager v16.0.0.118 was discovered to connect services to the named p
Phoneservice module is affected by code injection vulnerability, successful exploitation of this vulnerability may affec
There is a whitelist mechanism bypass in GameCenter ,successful exploitation of this vulnerability may affect service co
Local privilege escalation in Honor AiAssistant (all versions) allows authenticated users with low privileges to gain fu
Some Honor products are affected by file writing vulnerability, successful exploitation could cause code execution. Rate
Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause de
Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause de
Some Honor products are affected by incorrect privilege assignment vulnerability, successful exploitation could cause de
Some Honor products are affected by type confusion vulnerability, successful exploitation could cause information leak.
Some Honor products are affected by signature management vulnerability, successful exploitation could cause the forged s
Some Honor products are affected by signature management vulnerability, successful exploitation could cause the forged s
Honor E App discloses sensitive information to unauthorized users via network-accessible endpoints, requiring user inter
GitHub PoC
Exploit-DB