CVE-2025-14021VulnerabilityPublished 15 Dec 2025

CVE-2025-14021: LINE client for iOS · na

Affects LINE client for iOSSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 14.14 : update LINE client for iOS when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 14.14

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
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: None: There is no loss of confidentiality within 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
SwiftURLline/line-client-ios`pkg:swift/line/line-client-ios`Other threats	Affected =14.13	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to update the LINE client for iOS to version 14.14 or later, where the vulnerability has been addressed. Organizations should enforce mobile device management (MDM) policies that mandate timely application updates for corporate and BYOD devices. User education is critical: train employees to recognize phishing attempts, especially those originating from in-app browsers, and to verify URLs through external browsers when in doubt. Implement network-level protections such as DNS filtering and web proxies that can detect and block known phishing domains. Consider disabling or restricting the use of in-app browsers within LINE if feasible, or use security solutions that monitor app behavior for suspicious activity. Regularly audit and monitor for unusual login patterns or access attempts that could indicate credential compromise stemming from phishing. Finally, maintain an incident response plan that includes steps for addressing phishing incidents originating from mobile applications.

Description

The in-app browser in LINE client for iOS versions prior to 14.14 is vulnerable to address bar spoofing, which could allow attackers to execute malicious JavaScript within iframes while displaying trusted URLs, enabling phishing attacks through overlaid malicious content.

Impact

For European organizations, the impact of CVE-2025-14021 lies primarily in the potential for phishing attacks that could lead to credential theft, unauthorized access, and subsequent compromise of corporate accounts or sensitive information. Since LINE is popular in several European countries for both personal and professional communication, employees using vulnerable versions of the iOS client may be targeted by attackers leveraging this spoofing vulnerability. This could facilitate spear-phishing campaigns that bypass traditional email filters by exploiting trusted communication channels. The integrity of user interactions is compromised, potentially leading to financial fraud, data breaches, or lateral movement within corporate networks if attackers gain access to internal systems. Although the vulnerability does not directly affect confidentiality or availability, the indirect consequences of successful phishing can be severe. Organizations with BYOD policies or those that rely on LINE for customer engagement should be particularly vigilant. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers often weaponize such vulnerabilities once publicly disclosed.

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/2548498 (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