CVE-2026-47319

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.

Memory allocation with excessive size value vulnerability in Samsung Open Source rlottie allows Excessive Allocation.

This issue affects rlottie: before 0b4e308fa88c72cbb60cc8a2c1d2c2ad89b101dd.

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

fixed vpath potential issue

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

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

Vendor Advisories for CVE-2026-47319(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-08-25ubuntu

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-4, 0.1+dfsg-4+deb12u10.1+dfsg-4+deb12u2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rlottie0.1+dfsg-4.2, 0.1+dfsg-4.2+deb13u10.1+dfsg-4.2+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rlottie0.1+dfsg-4.2, 0.1+dfsg-4.30.1+dfsg-5—

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 16× in last 7d / 84× 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 180 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47319?
CVE-2026-47319 is a medium vulnerability published on June 4, 2026. Memory allocation with excessive size value vulnerability in Samsung Open Source rlottie allows Excessive Allocation. This issue affects rlottie: before 0b4e308fa88c72cbb60cc8a2c1d2c2ad89b101dd.
When was CVE-2026-47319 disclosed?
CVE-2026-47319 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-47319 actively exploited?
CVE-2026-47319 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-47319?
CVE-2026-47319 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-47319?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47319, 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-47319

Explore →

Is Your Infrastructure Affected by CVE-2026-47319?

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

Start Free Scan →Browse All CVEs