XAAP Application EUVD-2026-51576

Exploitation requires the target Android device to be jailbroken or otherwise compromised (rooted), granting the attacker elevated filesystem access beyond the normal Android app sandbox. The attacker must have local access to the device - either physical possession or logical access via a co-resident malicious app with root privileges. The XAAP Application must be installed and have stored sensitive data on that device. What limits exploitation: this is not a remote attack - no network exposure is involved; the prerequisite device compromise is itself a significant barrier; confidentiality impact is rated partial (VC:L), suggesting not all sensitive data may be exposed. Authentication to the device OS at elevated privilege level (root) is required, which the CVSS PR:L metric partially captures.

The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N) scores 4.8, reflecting that exploitation is constrained to local access on an already-compromised device. The attack vector is local and requires low privileges, meaning the attacker must have already achieved device compromise (jailbreak or root) before this vulnerability is exploitable - the CVE itself is not the initial access vector but a secondary data-exposure risk. No EPSS data or KEV listing is present in the provided intelligence, and no POC is reported, suggesting no known active exploitation. The confidentiality impact is rated low, implying partial rather than full data exposure. Overall, this is a moderate-severity data-at-rest hygiene issue rather than a remotely exploitable critical flaw; it represents a meaningful risk for threat models involving insider access, stolen devices, or MDM bypass, but is a low operational priority absent evidence of targeting.

An attacker who has already rooted an Android device - whether through physical access, a prior malware infection, or a supplied jailbroken device - navigates to the XAAP Application's private data directory and reads locally stored files containing sensitive information in cleartext. No special tooling beyond standard root file system access is required. No public POC has been identified, but the technique is trivially known and requires no vulnerability research.