Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain man-in-the-middle network position
-
ExploitIntercept app's cleartext traffic
-
ImpactCapture sensitive data in plaintext
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V12 - Secure Communication Transport encryption
|
| Exploitation Conditions | The AndroidManifest.xml Network Security Configuration of HeyCyan App 1.0.103 permits cleartext (non-TLS) transmission, so sensitive data can be observed by anyone who can inspect the app's network traffic. Realistic exploitation therefore requires the attacker to hold a man-in-the-middle position on the victim's network path (hostile hotspot, ARP/DNS spoofing, or a compromised network hop) - reflected in the AC:H / 'difficult' rating. Limiting factors: exploitation is passive-interception dependent (no server-side trigger), impact is confidentiality-only, it affects the specific Android build 1.0.103, and the exact sensitive data exposed is not described in the available sources. No authentication is required (PR:N) and no user interaction is specified (UI:N). |
| Impact | This is a moderate-severity information-disclosure issue (CVSS 4.0 base 6.3) that the signals consistently place below urgent priority. The vuln.today decision label is 'this_month' - not act_now or emergency - which aligns with the CVSS vector's high attack complexity (AC:H) and the vendor's own statement that exploitability is 'difficult.' The CVSS vector reports AV:N/PR:N/UI:N, so exploitation is network-based and requires no authentication, but AC:H means the attacker must satisfy non-trivial conditions (in practice, a man-in-the-middle position on the victim's network path to observe or downgrade traffic). Impact is limited to confidentiality (VC:L; VI:N/VA:N) - no integrity or availability effect. There is no CISA KEV listing and no EPSS score supplied in the input, so there is no evidence of active or widespread exploitation; a public PoC reference exists (a GitHub repository) but it is not verified as working exploit code. Net assessment: a real but low-urgency weakness - the lack of transport hardening is a genuine defect, but high complexity, confidentiality-only impact, and the absence of exploitation evidence mean this is not an emergency. All intelligence here derives from a single reporter (VulDB), which limits corroboration. |
| Exploit ScenarioDerived | An attacker positioned on the same network path as a victim (e.g., a hostile Wi-Fi hotspot or a compromised upstream hop) intercepts traffic from the HeyCyan Android app, whose Network Security Configuration permits cleartext transmission, and reads sensitive data sent in plaintext. A public PoC reference exists on GitHub but is not verified as working exploit code. The AC:H rating reflects that the attacker must first achieve this interception position, which is not guaranteed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Cleartext transmission of sensitive information in HeyCyan App 1.0.103 on Android arises from the app's Network Security Configuration in AndroidManifest.xml, which permits non-TLS traffic that can be passively observed by anyone able to inspect the app's network path. Realistic exploitation requires the attacker to already hold a man-in-the-middle position - a hostile hotspot, ARP/DNS spoofing, or a compromised network hop - which is why the issue is rated high complexity despite needing no authentication or user interaction. Impact is confidentiality-only, the specific data exposed is not described in the available sources, and no public exploit code is confirmed; the vendor was contacted about the disclosure but did not respond, and the available signals place this below urgent priority.
RemediationAI
No vendor-released patch identified at time of analysis: HeyCyan was contacted early about the disclosure and did not respond, so no fixed version number can be cited for the 1.0.103 Android build. Because the exposure depends on an attacker holding a man-in-the-middle position, the practical compensating control is to constrain the app to trusted network paths - avoid using it over open or hostile Wi-Fi hotspots and untrusted captive portals, which removes the interception vantage point the flaw requires, at the cost of restricting where the app can be used. Device-side protections that detect or block ARP/DNS spoofing and rogue access points reduce the same precondition but are not a complete fix, since a compromised upstream hop still defeats them. No configuration toggle inside the app is documented in the available sources as disabling the cleartext behavior, and modifying AndroidManifest.xml is not feasible for ordinary installers of a distributed APK. Monitor https://vuldb.com/vuln/426173 and https://github.com/azurejoga/heycyan-vulnerabilitys for any vendor response or updated build, and treat any credentials or personal data entered into the app over untrusted networks as potentially disclosed.
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
The root cause class is CWE-319 (Cleartext Transmission of Sensitive Information). Android's Network Security Configuration, declared through the android:networkSecurityConfig attribute in AndroidManifest.xml, controls whether an app permits cleartext HTTP or other non-TLS traffic per domain. In HeyCyan App 1.0.103 the configuration is reported to allow cleartext transmission, so application-layer data can traverse the network unencrypted and be captured by an observer positioned on the path. Because the flaw is configuration-based rather than a server-triggered memory or logic bug, there is no remotely invocable server-side trigger: the attacker must already sit between the device and its endpoint. The affected package is identified by CPE cpe:2.3:a:n/a:heycyan_app:*:*:*:*:*:*:*:*, and the precise manifest directive responsible, the specific traffic affected, and the exact sensitive data exposed are not described in the available sources.
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:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable cleartext but requires a MITM position (AC:H); no auth or interaction needed (PR:N/UI:N); confidentiality-only exposure (C:L), no integrity or availability impact.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
DescriptionCVE.org
A weakness has been identified in HeyCyan App 1.0.103 on Android. Affected is an unknown function of the file AndroidManifest.xml of the component Network Security Configuration. Executing a manipulation can lead to cleartext transmission of sensitive information. The attack can be launched remotely. The attack requires a high level of complexity. The exploitability is told to be difficult. 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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-109593
GHSA-6qxx-xgg9-2xr8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB