# CVE-2026-91826: Memory corruption in rLottie

> Attackers can trigger memory corruption via crafted vector animations in the rLottie library, potentially leading to code execution or crashes.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **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:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-91826, GHSA-27vc-rxrh-6fxx, UBUNTU-CVE-2026-91826

## What is CVE-2026-91826?

CVE-2026-91826 is a medium-severity memory corruption vulnerability in Samsung Opensource rLottie, published on 15 Sep 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

Stack-based buffer overflow vulnerability in Samsung Opensource rLottie allows attackers to overflow buffers, leading to memory corruption when rendering crafted vector animations.

This issue affects rLottie: 480a2ad0c5d2e45458c545b8213279e9e8b71e39.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

No fix has been published for CVE-2026-91826 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91826 is a medium-severity memory corruption vulnerability in Samsung Opensource rLottie, published on 15 Sep 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-91826 in the wild and no public exploit code.

Affected product: Samsung Opensource 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-91826/ (Markdown: https://insights.sbomify.com/CVE-2026-91826/index.md)
```

## Sources

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

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