rLottie
Samsung Open Source- Software type
- —
- Catalog vulnerabilities
- 18
Severity across 12 analyzed records
Verify to analyze this security profile
A short verification protects source data and prevents automated AI requests.
en
Severity across 12 analyzed records
A short verification protects source data and prevents automated AI requests.
As of 09/11/2026, within CyStack's analyzed data, rLottie has 1 security vulnerability published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of rLottie and determine which vulnerabilities affect that version.
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
| CVE | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-82797CVE-2026-82797 | Exploitation statusNot known exploited | FixYes | Published08/31/2026 | SeverityMedium |
CVE-2026-19588CVE-2026-19588 | Exploitation statusNot known exploited | FixNot confirmed | Published08/12/2026 | SeverityMedium |
CVE-2026-19587CVE-2026-19587 | Exploitation statusNot known exploited | FixNot confirmed | Published08/12/2026 | SeverityMedium |
CVE-2026-19518CVE-2026-19518 | Exploitation statusNot known exploited | FixNot confirmed | Published08/11/2026 | SeverityMedium |
CVE-2026-19517CVE-2026-19517 | Exploitation statusNot known exploited | FixNot confirmed | Published08/11/2026 | SeverityMedium |
CVE-2026-18772CVE-2026-18772 | Exploitation statusNot known exploited | FixNot confirmed | Published08/04/2026 | SeverityMedium |
CVE-2026-15551Samsung rlottie: Numeric truncation in gray_hline() leads to heap-based buffer overflow when rendering a crafted Lottie animation at native canvas size | Exploitation statusNot known exploited | FixNot confirmed | Published07/13/2026 | SeverityMedium |
CVE-2026-8916CVE-2026-8916 | Exploitation statusNot known exploited | FixNot confirmed | Published06/04/2026 | SeverityMedium |
CVE-2026-47318CVE-2026-47318 | Exploitation statusNot known exploited | FixNot confirmed | Published06/04/2026 | SeverityMedium |
CVE-2026-47306CVE-2026-47306 | Exploitation statusNot known exploited | FixNot confirmed | Published06/04/2026 | SeverityMedium |
CVE-2026-49510CVE-2026-49510 | Exploitation statusNot known exploited | FixNot confirmed | Published06/04/2026 | SeverityMedium |
CVE-2026-10305CVE-2026-10305 | Exploitation statusNot known exploited | FixNot confirmed | Published06/04/2026 | SeverityMedium |
CVE-2026-47319CVE-2026-47319 | Exploitation statusNot known exploited | FixNot confirmed | Published06/04/2026 | SeverityMedium |
CVE-2026-47320CVE-2026-47320 | Exploitation statusNot known exploited | FixNot confirmed | Published06/04/2026 | SeverityMedium |
CVE-2025-53074CVE-2025-53074 | Exploitation statusNot known exploited | FixNot confirmed | Published06/30/2025 | SeverityMedium |
CVE-2025-53076CVE-2025-53076 | Exploitation statusNot known exploited | FixNot confirmed | Published06/30/2025 | SeverityMedium |
CVE-2025-53075CVE-2025-53075 | Exploitation statusNot known exploited | FixNot confirmed | Published06/30/2025 | SeverityMedium |
CVE-2025-0634CVE-2025-0634 | Exploitation statusNot known exploited | FixNot confirmed | Published06/30/2025 | SeverityMedium |