Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious co-resident app
-
ExploitTarget exported FileProvider
-
ExecutionBypass improper access controls
-
ImpactRead or write protected app files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation targets the Android FileProvider component of HeyCyan App 1.0.103, where improper access controls (CWE-284) allow unauthorized access to files the provider should protect. The precise trigger is not described in the available sources. Realistically this class of flaw requires a malicious application co-resident on the same device to interact with the exported/misconfigured FileProvider, which limits exploitation to devices where such an app is installed - contradicting the input's 'remote' claim. Limiting factors: the specific affected build (1.0.103), the small installed base of this app, and the Low-rated impact scope (constrained file read/write, no availability effect). No vendor-confirmed configuration prerequisites are available because the vendor did not respond. |
| Impact | This is a medium-severity issue (CVSS 4.0 base 6.9) with no sign of being a high-priority emergency. Key signals: no CISA KEV listing (not confirmed actively exploited), no EPSS score provided in the input (exploitation probability cannot be quantified from available data), and a public PoC reference exists on GitHub but is not verified as working exploit code. The vuln.today decision label is 'this_month' - not act_now or emergency - which aligns with routine remediation rather than urgent patching. A significant conflict must be flagged: the supplied CVSS 4.0 vector claims a network attack vector (AV:N) and the description says 'the attack may be initiated remotely,' yet the component is an Android FileProvider with a CWE-284 improper-access-control weakness; such flaws are characteristically abused by a co-resident malicious app on the same device (a local vector), not by an unauthenticated network attacker - verify the true vector with the vendor or researcher. The impact is uniformly rated Low across confidentiality, integrity, and availability (VC:L/VI:L/VA:L), consistent with constrained file-level exposure rather than full device compromise. Net: a real but low-urgency issue, more a hygiene fix than a priority, and the 'remote' framing should be treated skeptically. |
| Exploit ScenarioDerived | A malicious or trojanized app installed alongside HeyCyan 1.0.103 on the same Android device abuses the misconfigured FileProvider to read or write files that should be protected by access controls, exposing limited app data. A public PoC reference exists on GitHub (azurejoga/heycyan-vulnerabilitys) but is not verified as working exploit code. The input's 'remote' characterization is doubtful for a FileProvider access-control flaw, which typically requires a co-located application rather than purely network access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Improper access controls in the Android FileProvider component of HeyCyan App 1.0.103 allow an attacker to reach files the provider is supposed to protect, with low-rated confidentiality and integrity impact and no availability effect. The vendor was contacted about the disclosure and did not respond, and no vendor-released patch has been identified; the CVE is not listed in CISA KEV and no EPSS score was supplied, though a public PoC reference (a GitHub repository linked from the VulDB entry) exists and is not verified as working exploit code. Note that the app's own CVSS 4.0 vector claims a network attack vector (AV:N), while the independent assessment rates this as a local (AV:L) issue: the realistic path is a malicious application co-resident on the same Android device interacting with the misconfigured provider, so exposure is limited to users of this specific build who install other apps alongside it.
RemediationAI
No vendor-released patch has been identified at time of analysis: HeyCyan was contacted and did not respond, so there is no fixed version to cite and no official advisory beyond the VulDB records at https://vuldb.com/vuln/426174 and https://vuldb.com/cve/CVE-2026-116106. Because the defect lives in the app's own FileProvider configuration, it cannot be corrected by device settings; the only complete fix is an updated build from the vendor, so users should watch those entries for a corrected release. Compensating measures, with their trade-offs: uninstall HeyCyan App 1.0.103 if it is not actively needed, which removes the exposed provider entirely but forfeits the app's functionality; on devices where it must stay, restrict installation of untrusted or sideloaded applications and review existing app inventory, since the practical attack path requires a co-resident malicious app, at the cost of reduced flexibility for users who sideload; and treat the app's shared/exported files as potentially readable by other apps, avoiding storage of sensitive documents through it. Enterprise deployments should flag the package in mobile threat defense or app-inventory tooling and treat any unexplained file access by other apps on the same device as suspicious, noting that these controls reduce but do not eliminate exposure while no vendor fix exists.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
FileProvider is the Android content-provider subclass used to hand out content:// URIs for an app's private files instead of file:// paths. Its security depends entirely on configuration: which path roots are declared, whether the provider is exported, and how URI permission grants are scoped. A CWE-284 (Improper Access Control) flaw here means the provider does not adequately restrict which calling applications can read or write the exposed files, so a caller the developer did not intend to trust can obtain access. The supplied CPE (cpe:2.3:a:n/a:heycyan_app, version wildcard with no vendor field) does not identify a concrete vendor product or version range, so only the description's stated build, HeyCyan App 1.0.103 on Android, is confirmed. Importantly, the two severity assessments diverge on the attack vector: the app-side CVSS 4.0 vector (AV:N, AC:L, PR:N, UI:N, VC:L/VI:L/VA:L) describes network reachability, whereas the independent assessment applies AV:L with PR:N and UI:N. Android's app sandbox means a provider misconfiguration of this class is normally exercised by another app already running on the same device, which is consistent with the local vector; the trigger mechanism itself is not described in the available sources, and no vendor-confirmed configuration prerequisites exist because the vendor never responded.
Know when Heycyan App 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Android FileProvider access-control flaws are abused by a co-resident app, so AV:L not AV:N; limited file read/write gives C:L/I:L and no availability impact (A:N).
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
DescriptionCVE.org
A security vulnerability has been detected in HeyCyan App 1.0.103 on Android. Affected by this vulnerability is an unknown functionality of the component FileProvider. The manipulation leads to improper access controls. The attack may be initiated remotely. The vendor was contacted early about this disclosure but did not respond in any way.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-109594
GHSA-gcgv-3j6w-p5vj
NVD
CVE.org
EPSS
VulDB
Exploit-DB