Cyber Resilience

CVE-2024-7014

High

Published: 23 July 2024

Published
23 July 2024
Modified
09 February 2026
KEV Added
Patch
CVSS Score v4 7.1 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.1755 95.2th percentile
Risk Priority 25 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2024-7014 is a high-severity Improper Input Validation (CWE-20) vulnerability in Telegram Telegram. Its CVSS base score is 7.1 (High).

Operationally, ranked in the top 4.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis

The EvilVideo vulnerability tracked as CVE-2024-7014 affects the Telegram for Android application in versions 10.14.4 and older. It arises from improper input validation (CWE-20) that permits malicious Android application packages to be presented and transmitted in the guise of ordinary video files, carrying a CVSS 4.0 score of 7.1.

An authenticated Telegram user can send such a disguised package to a target; if the recipient interacts with the message, the flaw can be leveraged to achieve high impact on the integrity and availability of the victim application and, via scope, on the broader system.

Reference analysis published by ESET details the technical mechanics of the issue and its exploitation path in Telegram. The associated EPSS score rose from lower values to a peak of 0.2569 on 2025-12-18 before receding to the current 0.1755, indicating that exploitation interest increased after public disclosure.

EU & UK References

Vulnerability details

EvilVideo vulnerability allows sending malicious apps disguised as videos in Telegram for Android application affecting versions 10.14.4 and older.

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

telegram
telegram
≤ 10.14.5

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-20

Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.

addresses: CWE-20

Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.

addresses: CWE-20

Directly implements checks on information inputs to reject invalid data before processing.

addresses: CWE-20

Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.

References