LY LINE client for iOS denial of service via recursion in Flex Message handling
- Exploited
- No known exploitation
- Fix
- Fixed in 26.19.0
- Who is exposed
- Not reported
Summary
LY Corporation's LINE client for iOS has an uncontrolled recursion flaw in how it processes Flex Message content. A remote attacker with low-privilege access can send a crafted message that crashes the app when the victim receives or displays it, and the victim must take some action for this to happen.
Written by a model
Original description
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.
What to do
Upgrade to a fixed version: 26.19.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-102430 (An uncontrolled recursion vulnerability exists in the LINE iOS app prior to version 26.19.0.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-102430 (entry last updated 2026-11-20):
Affected:
- LY Corporation LINE client for iOS: fixed in 26.19.0
Fixed versions: 26.19.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-102430 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-102430 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://line.github.io/security-advisory-blog/CVE-2026-102430/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-102430
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-102430"}.Affected versions
- LY Corporation LINE client for iOSfixed in 26.19.0
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.9/10CVSS 6.9
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-102430 |
| Record | NVD · CVE-2026-102430 |
| Other links 1 | |
| Link | line.github.io · security-advisory-blog/CVE-2026-102430 |
Questions about CVE-2026-102430
Is CVE-2026-102430 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-102430?
LINE client for iOS: before 26.19.0.
Source: cve.now feed data
How do I fix CVE-2026-102430?
Upgrade to a fixed version: 26.19.0.
Source: cve.now feed data
Related
- CVE-2026-3861LINE client for iOS versions prior to 26.3.0 contains a vulnerability in the in-app browser where opening a crafted web page can repeatedly
- CVE-2026-11746A vulnerability has been identified in centraldogma-server versions prior to 0.84.0, where enabling ZooKeeper replication without setting re
- CVE-2026-11751A vulnerability has been identified in armeria-xds versions prior to 1.41.0, where xDS upstream TLS peer verification may be silently…
- CVE-2026-11745A vulnerability has been identified in centraldogma-server-mirror-git versions prior to 0.84.0, where the Git mirror SSH client does not ver
- CVE-2026-121824A vulnerability has been identified in armeria versions prior to 1.43.0, where processing malformed Thrift messages can cause excessive…
- CVE-2026-121823A vulnerability has been identified in armeria versions prior to 1.43.0, where inconsistent request path normalization can allow…
No corrections so far. Something wrong on this page? Report an error.