Quick answers
- Is CVE-2026-49509 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49509 being exploited in the wild.
- How severe is CVE-2026-49509?
- Medium severity, with a CVSS score of 4.4, published 4 September 2026.
- Which products and versions are affected?
- Samsung Rlottie up to commit 25648aef19187b3f87f4d9420b8d761453ad4630.
- Is there a fix for CVE-2026-49509?
- A patch was published on 2026-09-01: Fix merged in PR #604 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49509 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-49509?
- 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
This is an out-of-bounds read vulnerability in the stb_image image processing component embedded within Samsung rLottie. The vulnerability stems from improper handling of fractional aspect ratios during image decoding, allowing an attacker to read memory outside the intended buffer boundaries. The issue affects commit 25648aef19187b3f87f4d9420b8d761453ad4630 and requires processing a malformed image or animation file through the rLottie renderer. An attacker can trigger memory disclosure or application denial-of-service. A fix was applied in PR #604 (merged September 1, 2026), aligning the code with stb_image 2.27 fixes for fractional ratio handling.
Affected products
- Samsung rLottie up to commit 25648aef19187b3f87f4d9420b8d761453ad4630
Timeline
- 2026-09-04: disclosed
- 2026-09-01: patched: Fix merged in PR #604