CVE-2025-14020VulnerabilityPublished 15 Dec 2025

CVE-2025-14020: LINE client for Android · na

Affects LINE client for AndroidSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
LINE Corporation LINE client for Android	Affected =10.0	Fixed in–

AI-suggested

1. Update the LINE client for Android to version 14.20 or later as soon as the patch is released to ensure the UI spoofing vulnerability is resolved. 2. Educate users about the risks of phishing attacks within in-app browsers, emphasizing caution when switching between apps and interacting with unexpected UI elements. 3. Implement mobile device management (MDM) policies that enforce app updates and restrict installation of outdated or untrusted applications. 4. Encourage users to verify URLs and security indicators manually when using in-app browsers, and to avoid entering sensitive information unless certain of the legitimacy. 5. Monitor for suspicious activity related to phishing attempts targeting LINE users, including unusual login patterns or reports of credential compromise. 6. Consider deploying endpoint protection solutions that can detect and block phishing attempts or malicious web content within mobile environments. 7. Collaborate with LINE Corporation for timely vulnerability disclosures and patch availability notifications.

Description

LINE client for Android versions prior to 14.20 contains a UI spoofing vulnerability in the in-app browser where the full-screen security Toast notification is not properly re-displayed when users return from another application, potentially allowing attackers to conduct phishing attacks by impersonating legitimate interfaces.

Impact

For European organizations, this vulnerability poses a moderate phishing risk, especially in sectors where LINE is widely used for communication, such as in multinational corporations with Asian-European ties or companies with employees who use LINE for business communications. Attackers could exploit this UI spoofing flaw to impersonate trusted interfaces, potentially leading to credential theft, unauthorized access, or data leakage. The impact on confidentiality and integrity is limited but non-negligible, as phishing attacks can facilitate further compromise. Since the vulnerability requires user interaction and targets the in-app browser, the scope is limited to users who browse web content within LINE and switch between apps frequently. The absence of known exploits reduces immediate risk, but the potential for social engineering attacks remains. Organizations with employees using Android devices and LINE should consider this vulnerability in their threat models, particularly in industries with high phishing exposure such as finance, healthcare, and government.

CWE-451User Interface (UI) Misrepresentation of Critical Information (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The user interface (UI) does not properly represent critical information to the user, allowing the information - or its source - to be obscured or spoofed. This is often a component in phishing attacks.
Implementation · Input Validation
Perform data validation (e.g. syntax, length, etc.) before interpreting the data.
Architecture and Design · Output Encoding
Create a strategy for presenting information, and plan for how to display unusual characters.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Spear Phishing (opens in a new tab)
Mobile Phishing (opens in a new tab)
Phishing (opens in a new tab)
Resource Location Spoofing (opens in a new tab)
Action Spoofing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

hackerone.com/reports/2547989 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Dec 2025, 07:21 UTC

WeaknessesCWE-451

Technical details

References

Community reviews

Related threats