Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft Lottie file with >32,767 path contours
-
DeliveryDeliver malicious file to target system
-
ExploitUser opens file in rlottie-embedded application
-
ExecutionShort integer truncation corrupts n_contours/n_points fields
-
PersistOut-of-bounds write in FreeType rasterizer
-
ImpactApplication crash or limited memory corruption
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires two concrete prerequisites confirmed by the CVSS vector: (1) local access - the attacker must be able to place or deliver a crafted Lottie animation file to the victim's system or platform (AV:L), and (2) user interaction - a user must explicitly open, render, or play the malicious animation file in an application embedding the vulnerable rlottie library (UI:R). The vulnerability is triggered specifically when rlottie processes a Lottie animation whose total contour count or point count in path geometry exceeds 32,767, causing the short field truncation. No authentication is required from the attacker's perspective (PR:N). Exploitation is limited by: the local attack vector ruling out remote network delivery without a separate delivery mechanism; the user interaction requirement preventing silent background exploitation; and the scope being unchanged (S:U), meaning a successful exploit cannot escape the application's privilege boundary to affect other system components. |
| Impact | CVSS 6.1 (Medium) with vector AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H reflects a locally-exploitable, user-interaction-dependent vulnerability with no confidentiality impact. The local attack vector (AV:L) significantly limits network-based opportunistic exploitation. User interaction (UI:R) means an attacker cannot silently exploit this - a user must open or render a crafted animation file. No EPSS score was provided in the intelligence data, so exploitation probability cannot be quantified. No KEV listing exists, meaning CISA has not confirmed active exploitation. No public exploit code has been identified at time of analysis. Despite PR:N (no privileges required), the combination of AV:L and UI:R makes mass automated exploitation unlikely; realistic risk is targeted attack via malicious file delivery to users of rlottie-embedded applications. The high availability impact (A:H) suggests reliable crash potential once triggered, which is consistent with integer truncation causing wild pointer dereferences in the rasterizer. |
| Exploit ScenarioDerived | An attacker crafts a malicious Lottie JSON animation file containing path data with contour or point counts exceeding 32,767 - the maximum value of a signed 16-bit short integer. The file is delivered to a victim (via email attachment, web download, or embedded in content on a Samsung TV platform) and the user opens or plays it in an rlottie-based application. The truncated short values corrupt pointer arithmetic in the FreeType rasterizer's ft_stroke_border_export() function, producing an out-of-bounds write that crashes the application or, in a less controlled scenario, corrupts adjacent memory structures. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 04, 2026
Out-of-bounds write in Samsung's rlottie animation rendering library allows a crafted Lottie animation file to trigger integer truncation in the embedded FreeType rasterizer, causing memory corruption. All rlottie versions before commit dcfde72eae1b0464dc0dd760aec00ada6a148635 are affected, spanning any downstream product or platform embedding this library (including Samsung TV and appliance firmware). Exploitation requires local access and user interaction to render a malicious animation, with primary impact being high availability loss (crash/DoS) and limited integrity impact; no public exploit identified at time of analysis and no active exploitation confirmed.
RemediationAI
Upgrade to the rlottie build containing commit dcfde72eae1b0464dc0dd760aec00ada6a148635, available via the upstream fix at https://github.com/Samsung/rlottie/pull/589. Note that no independently confirmed tagged release version is associated with this fix - the patch exists as a merged PR/commit, and a specific release version has not been confirmed in the available data. Downstream consumers of rlottie (e.g., Samsung TV/appliance firmware) should verify their vendor's advisory for a packaged fix version. As a compensating control where patching is not immediately possible, restrict the processing of untrusted or externally-sourced Lottie animation files within affected applications; this eliminates the attacker-controlled input path required to trigger the integer truncation. If rlottie is used in a sandboxed rendering process, ensuring that sandbox isolation is properly configured limits the blast radius of a successful crash to the sandbox context rather than the host application.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
rlottie (CPE: cpe:2.3:a:samsung_open_source:rlottie:*:*:*:*:*:*:*:*) is a Samsung Open Source C++ library for rendering Lottie JSON-based vector animations, embedded in Samsung TV and appliance firmware among other products. The vulnerability (CWE-787: Out-of-bounds Write) resides in the FreeType rasterizer component across three files: v_ft_raster.h, v_ft_stroker.cpp, and vraster.cpp. The root cause is integer width mismatch: fields n_contours and n_points, and the contours pointer array, were typed as short (SW_FT_Short, 16-bit signed, max 32,767). When processing complex Lottie animations whose contour or point counts exceed this limit, the values are silently truncated, causing incorrect pointer arithmetic in ft_stroke_border_export() and out-of-bounds writes into the outline buffer. The PR diff confirms the fix is a straightforward type widening: short/SW_FT_Short → int/SW_FT_Int across all relevant fields and casts, eliminating the truncation path.
Know when Samsung Open Source gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
Primary rating from Vendor (samsung.tv_appliance) · only source for this CVE.
CVSS VectorVendor: samsung.tv_appliance
DescriptionCVE.org
Out-of-bounds write vulnerability in Samsung Open Source rlottie allows Overflow Buffers.
This issue affects rlottie: before dcfde72eae1b0464dc0dd760aec00ada6a148635.
Zero Day Initiative Advisories
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Affected Products (CPE)CVE.org
More in Samsung Open Source
View allHeap buffer overflow in Samsung's rlottie animation rendering library allows remote denial-of-service via maliciously cr
Uncontrolled resource consumption in Samsung's open-source rlottie library allows a crafted Lottie animation file to tri
OS command injection in the Samsung QA-Board backend allows unauthenticated remote attackers to execute arbitrary operat
Out-of-bounds write in Samsung's Escargot lightweight JavaScript engine (commit 590345cc6258317c5da850d846ce6baaf2afc2d3
Heap-based buffer overflow in Samsung's Escargot JavaScript engine (commit 590345cc6258317c5da850d846ce6baaf2afc2d3) all
Use-after-free memory corruption in Samsung's Escargot JavaScript engine (commit 590345cc6258317c5da850d846ce6baaf2afc2d
Out-of-bounds write in Samsung's Escargot JavaScript engine allows attacker-supplied scripts to corrupt memory through t
Integer overflow in Samsung Escargot JavaScript engine allows remote attackers to trigger buffer overflows without authe
NULL pointer dereference in Samsung's open-source Walrus WebAssembly runtime crashes the parser when processing malforme
NULL pointer dereference in Samsung Open Source Walrus's WebAssembly binary parser causes application-level denial of se
Uncontrolled recursion in Samsung's Escargot JavaScript engine triggers excessive heap allocation, causing a denial-of-s
Denial of service in Samsung Escargot JavaScript engine at commit 590345cc6258317c5da850d846ce6baaf2afc2d3 stems from mu
EUVD-2026-34238
GHSA-598h-r4p3-q3wf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB