Quick answers
- Is CVE-2026-49510 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49510 being exploited in the wild.
- How severe is CVE-2026-49510?
- Medium severity, with a CVSS score of 6.1, published 4 June 2026.
- Which products and versions are affected?
- Samsung Rlottie before 21292665023e5074b38254432716866d00f1985f.
- Is there a fix for CVE-2026-49510?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-49510 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-49510?
- 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 integer overflow vulnerability exists in the Gradient::populate() function within src/lottie/lottiemodel.cpp of the Samsung rlottie library. The root cause is insufficient validation of the 'colorPoints' value (the 'g.p' field) from untrusted JSON input; specifically, values greater than or equal to 0x40000000 cause an overflow when multiplied by 4. This overflow results in a zero-value calculation that bypasses subsequent bounds checks, leading to a heap buffer over-read during gradient rendering. An attacker can exploit this by providing a malicious Lottie animation file, requiring local user interaction to open the file. The primary impact is a denial-of-service (crash), though it may also lead to minor integrity issues.
Affected products
- Samsung rlottie before 21292665023e5074b38254432716866d00f1985f
Timeline
- 2026-06-01: other: Fix proposed via GitHub Pull Request
- 2026-06-04: advisory: NVD publication date