# CVE-2026-47320: Memory corruption in rlottie

> An attacker can cause denial of service or potential code execution in applications using rlottie by providing oversized serialized data payloads.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jun 2026
- **Updated:** 7 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-47320, GHSA-gjw3-x488-w5c3, UBUNTU-CVE-2026-47320

## What is CVE-2026-47320?

CVE-2026-47320 is a medium-severity memory corruption vulnerability in Samsung Open Source rlottie, published on 4 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Access of uninitialized pointer, Uncontrolled Recursion vulnerability in Samsung Open Source rlottie allows Pointer Manipulation, Oversized Serialized Data Payloads.

This issue affects rlottie: before eae37633fda13ac05b25c6c95aacea4bc33c80a3.

Weakness: CWE-824 (Access of Uninitialized Pointer), CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-47320?


## How do I fix CVE-2026-47320?

Apply the vendor's patch.

## Is CVE-2026-47320 being exploited?

There is no known exploitation of CVE-2026-47320 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47320 and fix it if it is affected.

What it is: CVE-2026-47320 is a medium-severity memory corruption vulnerability in Samsung Open Source rlottie, published on 4 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-47320 in the wild and no public exploit code.

Affected product: Samsung Open Source rlottie. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47320/ (Markdown: https://insights.sbomify.com/CVE-2026-47320/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47320
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47320
- OSV: https://osv.dev/vulnerability/CVE-2026-47320

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47320/
Summaries are generated and may contain mistakes; the official description above is the record.