Quick answers
- Is CVE-2026-47306 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47306 being exploited in the wild.
- How severe is CVE-2026-47306?
- Medium severity, with a CVSS score of 6.1, published 4 June 2026.
- Which products and versions are affected?
- Samsung Rlottie before commit e2d19e3b150e0e4a9586fa90b56fd3061cc98945.
- Is there a fix for CVE-2026-47306?
- 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-47306 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-47306?
- 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
An uncontrolled recursion vulnerability (CWE-674) exists in Samsung's rlottie library due to improper handling of circular asset references within Lottie JSON files. Specifically, a malicious file containing self-referencing or mutually referencing 'precomp' assets triggers infinite recursion in renderer::CompLayer::CompLayer() via createLayerItem(). This exhaustion of stack space results in a SIGSEGV crash. The attack requires a user to open or load a specially crafted animation file. The issue was addressed by implementing a directed asset dependency graph and using Breadth-First Search (BFS) to detect and skip cyclic dependencies during the layer resolution phase.
Affected products
- Samsung rlottie before commit e2d19e3b150e0e4a9586fa90b56fd3061cc98945
Timeline
- 2026-04-28: disclosed: Vulnerability details and fix proposed in GitHub pull request
- 2026-05-12: patched: Fix merged into master branch
- 2026-06-04: advisory: CVE-2026-47306 published