Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious app on device
-
ExploitBind to unprotected FileRead AIDL service
-
ImpactSupply absolute path to read sandboxed files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the ProjectMAXS MAXS Module FileRead (versionCode 27) to be installed on the device, plus a second locally-installed app controlled by the attacker that can bind to the module's exported AIDL service, which lacks permission enforcement. The attacker then supplies an absolute path to read files beyond the caller's sandbox. Key limiting factors: this is local IPC exploitation (no remote/network reach despite the input's AV:N), the attacker must already have an app running on the device, and readable content is bounded by the permissions the MAXS module process itself holds rather than full-device access. |
| Impact | The provided CVSS base score is 7.5 (High), but the input vector contains two internal inconsistencies that materially change the real-world picture. First, the vector lists AV:N (network) even though the flaw is in an Android AIDL interface, which is a local inter-process communication mechanism - exploitation requires a malicious app already present on the same device, i.e. local attack vector, not remote network reach. Second, the vector sets C:N/I:H, yet the described impact is arbitrary file READING outside the sandbox, which is a confidentiality breach (should be C:H), not an integrity one; the I:H appears to be a scoring error. No EPSS probability was supplied, the CVE is not listed in CISA KEV, and no public exploit was identified at time of analysis - only a third-party GitHub advisory entry and the vendor repo are referenced. The vuln.today decision label is 'this_week' rather than act_now/emergency, consistent with a locally-exploitable disclosure flaw in a niche product. Net assessment: this is a genuine information-disclosure weakness but not a widespread-exploitation priority - the combination of local-only triggering, a tiny deployment base, and impact bounded by the MAXS module's own granted permissions places it well below the raw 7.5 would suggest. Treat the published AV:N/I:H vector as unreliable and verify with the advisory. |
| Exploit ScenarioDerived | A malicious or low-privilege app installed on an Android device that also runs the ProjectMAXS FileRead module (versionCode 27) binds to the module's improperly-protected AIDL service and passes an absolute filesystem path. Because the interface lacks permission enforcement, the module returns file contents from outside the caller's sandbox, limited to whatever the MAXS module process itself is permitted to read. No public working exploit code was identified; a third-party advisory documents the issue. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Unauthorized file read in the ProjectMAXS MAXS Module FileRead (versionCode 27) lets a locally installed attacker-controlled app bind to the module's exported AIDL service and pass an absolute path to read files that lie outside the caller's own sandbox. The exposure stems from missing permission enforcement on that inter-process interface, and the reachable data is limited to whatever the MAXS module's process itself can access, not full-device compromise. The supplied CVSS vector (AV:N, I:H, C:N) does not match the observed attack path, which is local IPC with no network reach and confidentiality impact only; no public exploit code and no confirmed active exploitation were identified at time of analysis.
RemediationAI
No vendor-released patch is identified in the available sources; the F-Droid package page (f-droid.org/packages/org.projectmaxs.module.fileread/) and the upstream repository (bitbucket.org/projectmaxs/maxs) should be monitored for a corrected build, and the advisory at github.com/FFG0d/fdroid-android-advisories/blob/main/advisories/CVE-2026-107052.md should be checked for an updated versionCode. Because the flaw is a missing permission check on an exported AIDL service, the most direct compensating control is to remove the exposure entirely: uninstall the FileRead module (or keep it off any device holding sensitive data) if its file-reading capability is not actively used, at the cost of losing that automation feature. Until a fixed build ships, treat the device as one where any installed app can read files accessible to the MAXS module process, so limit installation to trusted applications and avoid co-locating the module with apps of uncertain provenance; this reduces but does not eliminate the risk, since an already-installed malicious app retains the ability to bind the service. Restricting installation to a managed app catalogue or work profile is a further containment option, with the trade-off of reduced user flexibility and no change to the underlying interface flaw.
Affected VersionsENISA
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
ProjectMAXS is an Android automation framework distributed through F-Droid as modular packages, and the FileRead module (package org.projectmaxs.module.fileread, versionCode 27) exposes functionality to other apps through an Android Interface Definition Language (AIDL) bound service. The root cause class is CWE-276, Incorrect Default Permissions: the exported service does not enforce a caller permission, so any second application installed on the same device can bind to it and invoke the file-read method with an arbitrary absolute path, bypassing the normal per-app sandbox boundary. Because this is Binder/IPC rather than a socket or HTTP endpoint, the practical attack surface is the local device only; the framing of the input vector as AV:N and integrity-impacting (I:H, C:N) is inconsistent with the assessed vector (AV:L, S:C, C:H, I:N, A:N), which better reflects a local, cross-boundary confidentiality breach with no integrity or availability effect. The trigger conditions are explicit in the advisory: the module must be installed and the attacker must already have code executing as a second local app that can bind the service. What the attacker can read is bounded by the UID and permissions of the MAXS module process itself rather than by unrestricted device access.
Know when Android 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
AIDL is local on-device IPC so AV:L; any unprivileged app can bind so PR:N/UI:N; reading files outside the sandbox crosses a security boundary (S:C) and is confidentiality-only (C:H, I:N, A:N).
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
3DescriptionCVE.org
Insecure permissions in the AIDL interface of ProjectMAXS MAXS Module FileRead versionCode 27 allows unauthorized attackers to arbitrarily reead files outside of the sandbox via providing an absolute path.
Executive ViewAI
CVE-2026-107052 is a high-severity unauthorized file read vulnerability in the ProjectMAXS MAXS Module FileRead (versionCode 27) that allows a locally installed malicious app to bypass sandbox restrictions and access files readable by the MAXS module's process. While it does not enable full-device compromise, any sensitive data accessible to the MAXS module-such as configuration or user files-could be exposed to other apps on the device, affecting user privacy and data integrity. Security management should prioritize mitigation because unpatched devices remain vulnerable and the attack requires only local app installation, which is a low barrier for attackers.
No vendor patch is available. Interim mitigations: disable or uninstall the MAXS Module FileRead where feasible; restrict installation of third-party apps on affected devices; implement application allowlisting; monitor for anomalous inter-process communication or file access patterns; isolate affected devices from sensitive data stores.
Threat Intelligence Overview
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-113261
GHSA-669w-gvvp-f77q
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB