cve.bz

CVE-2026-18772 samsung rlottie

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in samsung rlottie. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Improperly controlled sequential memory allocation vulnerability in Samsung Open Source rlottie allows Exponential Data Expansion.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1325 Improperly Controlled Sequential Memory Allocation
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-18772 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18772?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18772?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-18772 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-18772

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-18772](https://cve.bz/cve/badge/CVE-2026-18772.svg)](https://cve.bz/cve/CVE-2026-18772)

HTML:

<a href="https://cve.bz/cve/CVE-2026-18772"><img src="https://cve.bz/cve/badge/CVE-2026-18772.svg" alt="CVE-2026-18772"></a>

Affected

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14rlottie0.1+dfsg-4DEBIAN-CVE-2026-18772
Ubuntu26.10, Pro:20.04:LTS, Pro:22.04:LTS and 2 morerlottieno fix listedUBUNTU-CVE-2026-18772

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON