CVE-2026-47318

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-06-04. a secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

A fix is available — apply it.

Stack-based buffer overflow vulnerability in Samsung Open Source rlottie allows Overflow Buffers.

This issue affects rlottie: before ce72b35a7ad0dded03051d3aa0ef75321c3bd035.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
27(Track)
EG Risk 27/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 computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 4, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

Fix stack overflow vulnerability in gray_render_cubic

Fix merged in Samsung/rlottie PR #582 on 2026-05-12 — awaiting tagged release

https://github.com/Samsung/rlottie/pull/582

Vendor Advisories for CVE-2026-47318(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibrlottie0-1 (0.1+dfsg-4.3ubuntu0.1~esm1) @ resolute2026-09-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rlottie0.1+dfsg-2, 0.1+dfsg-2+deb11u10.1+dfsg-2+deb11u2
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rlottie0.1+dfsg-3
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rlottie0.1+dfsg-3
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rlottie0.1+dfsg-3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 35× 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.

Showing the most recent 100 of 189 total refreshes for this CVE.

  1. 2026-09-14 05:27 UTCEG score recompute
  2. 2026-09-14 05:27 UTCVendor advisory
  3. 2026-09-14 05:27 UTCGHSA enrichment
  4. 2026-09-12 15:01 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:37 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 03:32 UTCEG score recompute
  20. 2026-08-25 03:32 UTCVendor advisory
  21. 2026-08-25 03:32 UTCGHSA enrichment
  22. 2026-08-23 12:43 UTCEG score recompute
  23. 2026-08-23 12:43 UTCVendor advisory
  24. 2026-08-23 12:43 UTCGHSA enrichment
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 14:37 UTCEG score recompute
  3. 2026-08-21 14:37 UTCVendor advisory
  4. 2026-08-21 14:37 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 09:58 UTCEG score recompute
  7. 2026-08-20 09:58 UTCVendor advisory
  8. 2026-08-20 09:58 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 03:26 UTCEG score recompute
  12. 2026-08-17 03:26 UTCVendor advisory
  13. 2026-08-17 03:26 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:16 UTCEG score recompute
  16. 2026-08-16 02:16 UTCVendor advisory
  17. 2026-08-16 02:16 UTCGHSA enrichment
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 23:05 UTCVendor advisory
  21. 2026-08-14 23:05 UTCGHSA enrichment
  22. 2026-08-13 22:56 UTCEG score recompute
  23. 2026-08-13 22:56 UTCVendor advisory
  24. 2026-08-13 22:56 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-12 22:47 UTCEG score recompute
  27. 2026-08-12 22:47 UTCVendor advisory
  28. 2026-08-12 22:47 UTCGHSA enrichment
  29. 2026-08-12 13:51 UTCEPSS rescore
  30. 2026-08-11 22:38 UTCEG score recompute
  31. 2026-08-11 22:38 UTCVendor advisory
  32. 2026-08-11 22:38 UTCGHSA enrichment
  33. 2026-08-11 00:00 UTCEPSS rescore
  34. 2026-08-10 22:29 UTCVendor advisory
  35. 2026-08-10 22:29 UTCGHSA enrichment
  36. 2026-08-09 21:05 UTCEG score recompute
  37. 2026-08-09 21:05 UTCVendor advisory
  38. 2026-08-09 21:05 UTCGHSA enrichment
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 20:57 UTCEG score recompute
  41. 2026-08-08 20:57 UTCVendor advisory
  42. 2026-08-08 20:57 UTCGHSA enrichment
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-07 20:48 UTCEG score recompute
  45. 2026-08-07 20:48 UTCVendor advisory
  46. 2026-08-07 20:48 UTCGHSA enrichment
  47. 2026-08-06 20:39 UTCEG score recompute
  48. 2026-08-06 20:39 UTCVendor advisory
  49. 2026-08-06 20:39 UTCGHSA enrichment
  50. 2026-08-06 13:47 UTCEPSS rescore
  51. 2026-08-05 20:30 UTCEG score recompute
  52. 2026-08-05 20:30 UTCVendor advisory
  53. 2026-08-05 20:30 UTCGHSA enrichment
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-04 19:10 UTCEG score recompute
  56. 2026-08-04 19:10 UTCVendor advisory
  57. 2026-08-04 19:10 UTCGHSA enrichment
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-03 15:41 UTCEG score recompute
  60. 2026-08-03 15:41 UTCVendor advisory
  61. 2026-08-03 15:41 UTCGHSA enrichment
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-02 13:05 UTCVendor advisory
  64. 2026-08-02 13:05 UTCGHSA enrichment
  65. 2026-08-01 12:56 UTCEG score recompute
  66. 2026-08-01 12:56 UTCVendor advisory
  67. 2026-08-01 12:56 UTCGHSA enrichment
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-31 05:27 UTCEG score recompute
  70. 2026-07-31 05:27 UTCVendor advisory
  71. 2026-07-31 05:27 UTCGHSA enrichment
  72. 2026-07-30 16:28 UTCEPSS rescore
  73. 2026-07-30 01:30 UTCEPSS rescore
  74. 2026-07-29 10:10 UTCEG score recompute
  75. 2026-07-29 10:10 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-47318?
CVE-2026-47318 is a medium vulnerability published on June 4, 2026. Stack-based buffer overflow vulnerability in Samsung Open Source rlottie allows Overflow Buffers. This issue affects rlottie: before ce72b35a7ad0dded03051d3aa0ef75321c3bd035.
When was CVE-2026-47318 disclosed?
CVE-2026-47318 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47318 actively exploited?
CVE-2026-47318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.8% of all scored CVEs.
What is the CVSS score of CVE-2026-47318?
CVE-2026-47318 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-47318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47318, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47318

Explore →

Is Your Infrastructure Affected by CVE-2026-47318?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.