# CVE-2026-47319: Denial of service in rlottie

> An attacker can cause a denial of service by triggering excessive memory allocation in the rlottie library.

- **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:** 8 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-47319, GHSA-5j7g-c464-cj57, UBUNTU-CVE-2026-47319

## What is CVE-2026-47319?

CVE-2026-47319 is a medium-severity denial of service 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

Memory allocation with excessive size value vulnerability in Samsung Open Source rlottie allows Excessive Allocation.

This issue affects rlottie: before 0b4e308fa88c72cbb60cc8a2c1d2c2ad89b101dd.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

Apply the vendor's patch.

## Is CVE-2026-47319 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47319 is a medium-severity denial of service 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-47319 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-47319/ (Markdown: https://insights.sbomify.com/CVE-2026-47319/index.md)
```

## Sources

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

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