CVE-2026-102430 in LINE
Summary
by MITRE • 11/20/2026
An uncontrolled recursion vulnerability exists in the LINE iOS app prior to version 26.19.0.
The Flex Message processing component does not adequately validate the structure of externally supplied message content.
As a result, an attacker who is able to send a crafted message to a victim could cause the application to crash when the message is received or displayed.
A server-side mitigation has been deployed that also protects existing iOS clients that have not been updated to version 26.19.0.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The vulnerability identified in LINE versions prior to 26.19.0 for iOS represents a critical flaw within the application's Flex Message processing component, specifically categorized under CWE-674 as Uncontrolled Recursion. This architectural weakness stems from an insufficient validation mechanism when parsing externally supplied message content structures. The Flex Message system is designed to render complex layouts and interactive elements based on JSON-like data provided by senders or servers. However, the parser fails to enforce strict limits on nesting depth or recursive structure complexity during the deserialization phase. When a specially crafted payload containing deeply nested objects or circular references is processed, the application's execution stack grows exponentially without proper boundary checks, leading directly to a stack overflow condition that forces an immediate termination of the process.
From an operational perspective, this vulnerability primarily facilitates Denial of Service attacks against end-users rather than remote code execution or data exfiltration in its current manifestation. An attacker capable of sending messages to victims can trigger application crashes simply by delivering these malformed payloads. While a crash is generally considered less severe than arbitrary code execution, it significantly degrades user experience and trust in the platform's stability. In mobile environments where applications are expected to remain responsive and stable during continuous use, frequent unexpected terminations constitute a substantial availability risk. Furthermore, if such crashes occur repeatedly or can be triggered via automated means against specific targets, they may serve as part of broader disruption campaigns aimed at hindering communication channels for targeted individuals or groups.
The technical classification aligns with CWE-20 Improper Input Validation and CWE-787 Out-of-bounds Write in the context of stack memory corruption due to recursion depth exceeding allocated limits. In terms of adversary tactics, this behavior corresponds to ATT&CK technique T1499 Endpoint Denial of Service, where an attacker leverages software vulnerabilities to disrupt service availability on specific endpoints. The lack of input sanitization regarding structural complexity allows external actors to exploit the resource consumption inherent in recursive parsing operations, turning a standard feature into a vector for instability.
Mitigation strategies have been implemented both client-side and server-side to address this issue comprehensively. On the client side, version 26.19.0 introduces enhanced validation logic within the Flex Message parser that strictly enforces maximum nesting depths and rejects payloads exceeding defined structural thresholds before they reach critical processing functions. This prevents the stack overflow condition from occurring by failing fast during input analysis rather than allowing execution to proceed into unsafe recursion patterns. Additionally, a server-side mitigation has been deployed which acts as an additional layer of defense for existing iOS clients that have not yet updated to version 26.19.0. By filtering or sanitizing malicious payloads at the infrastructure level before they reach user devices, LINE ensures protection across its entire active user base regardless of individual update status. Users are strongly advised to upgrade their applications immediately to ensure full compliance with these security enhancements and maintain optimal operational stability.