# CVE-2026-49510: Integer overflow in rlottie

> An integer overflow in the Samsung rlottie library can lead to denial of service, requiring users to update to a patched version.

- **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-49510, GHSA-fxgp-4mch-4c5h, UBUNTU-CVE-2026-49510

## What is CVE-2026-49510?

CVE-2026-49510 is a medium-severity 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

Integer overflow or wraparound vulnerability in Samsung Open Source rlottie allows Integer Attacks.

This issue affects rlottie: before 21292665023e5074b38254432716866d00f1985f.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

Apply the vendor's patch.

## Is CVE-2026-49510 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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