CVE-2026-116106 HeyCyan App FileProvider access control
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-116106 and fix it if it is affected.
What it is: CVE-2026-116106 is a medium-severity vulnerability in HeyCyan App, published on 26 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-116106 in the wild and no public exploit code.
Affected product: HeyCyan App. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-116106/ (Markdown: https://insights.sbomify.com/CVE-2026-116106/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116106?
CVE-2026-116106 is a medium-severity vulnerability in HeyCyan App, published on 26 Oct 2026.
Official description
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.
Which versions are affected by CVE-2026-116106?
How do I fix CVE-2026-116106?
No fix has been published for CVE-2026-116106 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116106 being exploited?
There is no known exploitation of CVE-2026-116106 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-gcgv-3j6w-p5vj.