Improperly controlled sequential memory allocation vulnerability in Samsung Open Source rlottie allows Exponential Data Expansion.
CVE-2026-18772
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 4, 2026
Last Modified
August 18, 2026
Advisory Details (1)
Auto-updated Aug 4, 2026Safety limits to precomp, repeater, and polystar handling
Fix merged in Samsung/rlottie PR #596 on 2026-07-22 — awaiting tagged release
https://github.com/Samsung/rlottie/pull/596Vendor Advisories for CVE-2026-18772(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rlottie | 0.1+dfsg-2 ... 0.1+dfsg-5 (9 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rlottie | 0.1+dfsg-4 ... 0.1+dfsg-5 (7 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rlottie | 0.1+dfsg-4.2, 0.1+dfsg-4.2+deb13u1, 0.1+dfsg-4.2+deb13u2, 0.1+dfsg-4.3, 0.1+dfsg-5 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| rlottie | 0.1+dfsg-4.2, 0.1+dfsg-4.3, 0.1+dfsg-5 | — | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 57× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 16:50 UTCEG score recompute
- 2026-08-20 16:50 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 16:19 UTCGHSA enrichment
- 2026-08-18 15:34 UTCEG score recompute
- 2026-08-18 15:34 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 03:32 UTCEG score recompute
- 2026-08-18 03:32 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 03:03 UTCEG score recompute
- 2026-08-17 03:03 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:34 UTCEG score recompute
- 2026-08-16 02:34 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 02:05 UTCEG score recompute
- 2026-08-15 02:05 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 01:37 UTCEG score recompute
- 2026-08-14 01:37 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 01:09 UTCEG score recompute
- 2026-08-13 01:09 UTCGHSA enrichment
Show 32 moreShow fewer
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 00:40 UTCEG score recompute
- 2026-08-12 00:40 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 05:24 UTCEG score recompute
- 2026-08-11 05:23 UTCGHSA enrichment
- 2026-08-11 05:08 UTCEG score recompute▲ 1.00
- 2026-08-11 05:08 UTCGHSA enrichment
- 2026-08-11 05:08 UTCMITRE cvelistV5CVSS v3 → 6.5
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 17:09 UTCGHSA enrichment
- 2026-08-09 16:40 UTCEG score recompute
- 2026-08-09 16:40 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 16:12 UTCEG score recompute
- 2026-08-08 16:12 UTCGHSA enrichment
- 2026-08-07 15:43 UTCGHSA enrichment
- 2026-08-06 15:15 UTCEG score recompute
- 2026-08-06 15:15 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 14:46 UTCEG score recompute
- 2026-08-05 14:46 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 14:18 UTCEG score recompute
- 2026-08-04 14:18 UTCGHSA enrichment
- 2026-08-04 13:59 UTCEG score recompute
- 2026-08-04 13:59 UTCGHSA enrichment
- 2026-08-04 10:31 UTCEG score recompute
- 2026-08-04 09:21 UTCEG score recompute
- 2026-08-04 09:20 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-18772?
When was CVE-2026-18772 disclosed?
Is CVE-2026-18772 actively exploited?
What is the CVSS score of CVE-2026-18772?
How do I remediate CVE-2026-18772?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18772
Is Your Infrastructure Affected by CVE-2026-18772?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.