Quick answers
- Is CVE-2026-47318 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47318 being exploited in the wild.
- How severe is CVE-2026-47318?
- Medium severity, with a CVSS score of 6.1, published 4 June 2026.
- Which products and versions are affected?
- Samsung Rlottie before ce72b35a7ad0dded03051d3aa0ef75321c3bd035.
- Is there a fix for CVE-2026-47318?
- A patch was published on 2026-05-12: Fix merged into master branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47318 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-47318?
- Check whether you run Samsung Rlottie at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow exists in the 'gray_render_cubic' function within Samsung's rlottie library. The vulnerability is caused by a lack of bounds checking before calling 'gray_split_cubic'. The function utilizes a fixed-size stack ('bez_stack') of 97 elements; however, certain cubic curve splits can cause the stack pointer to advance beyond this limit, leading to an out-of-bounds write at index 99. An attacker can exploit this by providing a malicious Lottie file with specifically crafted cubic curves. This requires local interaction (user opening a file) and can result in a denial of service or potential arbitrary code execution. The issue is addressed in commit ce72b35a7ad0dded03051d3aa0ef75321c3bd035.
Affected products
- Samsung rlottie before ce72b35a7ad0dded03051d3aa0ef75321c3bd035
Timeline
- 2026-04-10: disclosed: Initial pull request with fix submitted to GitHub
- 2026-05-12: patched: Fix merged into master branch
- 2026-06-04: advisory: NVD publication date