CVE-2025-0634

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: MODERATE) published 2025-06-30. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-19505 (ENISA EUVD) · GHSA-5cvm-3562-3m3m (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use After Free vulnerability in Samsung Open Source rLottie allows Remote Code Inclusion.This issue affects rLottie: V0.2.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 30, 2025

Last Modified

January 22, 2026

Advisory Details (2)

Auto-updated Oct 9, 2026
Patch available. Sources: github_commit, github_pr.
GitHub commit

commit 507ea027e47d (Samsung/rlottie)

Fix landed in Samsung/rlottie commit 507ea027e47d — awaiting tagged release

https://github.com/Samsung/rlottie/commit/507ea027e47d3e1dc7ddbd9994621215eae7ebb9
GitHub pull request

Fix security vulnerabilities in Lottie file handling

Fix merged in Samsung/rlottie PR #571 on 2025-06-11 — awaiting tagged release

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibrlottie0-1 (0.1+dfsg-2ubuntu0.2) @ jammy2026-11-12ubuntu

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 rangeFix by version rangeDependents
rlottie0.1+dfsg-2
  • every version up to 0.1+dfsg-2+deb11u1: fixed in 0.1+dfsg-2+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rlottie0.1+dfsg-4
  • every version up to 0.1+dfsg-4+deb12u1: fixed in 0.1+dfsg-4+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rlottie0.1+dfsg-4.2
  • every version up to 0.1+dfsg-4.2+deb13u1: fixed in 0.1+dfsg-4.2+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rlottie0.1+dfsg-4.2
  • every version up to 0.1+dfsg-4.3: fixed in 0.1+dfsg-4.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 16× in last 7d / 72× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 288 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 188 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 08:15 UTCEchelonGraph re-scored
  2. 2026-11-13 08:15 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  3. 2026-11-12 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-11-12 09:36 UTCEchelonGraph re-scored
  5. 2026-11-12 09:36 UTCVendor advisory
  6. 2026-11-12 09:36 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  7. 2026-11-11 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-11-11 10:58 UTCEchelonGraph re-scored
  9. 2026-11-11 10:58 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  10. 2026-11-10 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-11-10 12:19 UTCEchelonGraph re-scored
  12. 2026-11-10 12:19 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  13. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-11-09 13:41 UTCEchelonGraph re-scored
  15. 2026-11-09 13:41 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  16. 2026-11-08 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-11-08 15:04 UTCEchelonGraph re-scored
  18. 2026-11-08 15:03 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  19. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-11-07 16:24 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  21. 2026-11-06 17:44 UTCEchelonGraph re-scored
  22. 2026-11-06 17:44 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  23. 2026-11-06 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-11-05 19:06 UTCEchelonGraph re-scored
  25. 2026-11-05 19:06 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-05 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-05 06:55 UTCOSV refresh
  3. 2026-11-04 20:26 UTCEchelonGraph re-scored
  4. 2026-11-04 20:26 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  5. 2026-11-04 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-11-03 21:48 UTCEchelonGraph re-scored
  7. 2026-11-03 21:48 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  8. 2026-11-03 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-11-02 23:09 UTCEchelonGraph re-scored
  10. 2026-11-02 23:09 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  11. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-11-02 00:31 UTCEchelonGraph re-scored
  13. 2026-11-02 00:31 UTCVendor advisory
  14. 2026-11-02 00:31 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub severity MODERATE · GitHub CVSS 9.8
  15. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-11-01 01:53 UTCEchelonGraph re-scored
  17. 2026-11-01 01:53 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  18. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-31 03:15 UTCEchelonGraph re-scored
  20. 2026-10-31 03:15 UTCVendor advisory
  21. 2026-10-31 03:15 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  22. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-30 04:37 UTCEchelonGraph re-scored
  24. 2026-10-30 04:37 UTCVendor advisory
  25. 2026-10-30 04:37 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  26. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-10-29 05:59 UTCEchelonGraph re-scored
  28. 2026-10-29 05:59 UTCVendor advisory
  29. 2026-10-29 05:59 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  30. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-10-28 07:22 UTCEchelonGraph re-scored
  32. 2026-10-28 07:22 UTCVendor advisory
  33. 2026-10-28 07:21 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  34. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  35. 2026-10-27 08:44 UTCEchelonGraph re-scored
  36. 2026-10-27 08:44 UTCVendor advisory
  37. 2026-10-27 08:44 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  38. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-10-26 08:10 UTCVendor advisory
  40. 2026-10-26 08:10 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  41. 2026-10-25 16:49 UTCEchelonGraph re-scored
  42. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  43. 2026-10-25 09:33 UTCEchelonGraph re-scored
  44. 2026-10-25 09:33 UTCVendor advisory
  45. 2026-10-25 09:33 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  46. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  47. 2026-10-24 10:55 UTCEchelonGraph re-scored
  48. 2026-10-24 10:54 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  49. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  50. 2026-10-23 12:15 UTCEchelonGraph re-scored
  51. 2026-10-23 12:14 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  52. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  53. 2026-10-22 13:35 UTCEchelonGraph re-scored
  54. 2026-10-22 13:35 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  55. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  56. 2026-10-21 14:52 UTCEchelonGraph re-scored
  57. 2026-10-21 14:52 UTCVendor advisory
  58. 2026-10-21 14:52 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  59. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  60. 2026-10-20 15:55 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  61. 2026-10-19 17:11 UTCEchelonGraph re-scored
  62. 2026-10-19 17:10 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  63. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  64. 2026-10-18 18:32 UTCEchelonGraph re-scored
  65. 2026-10-18 18:32 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  66. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  67. 2026-10-18 05:53 UTCEchelonGraph re-scored
  68. 2026-10-17 19:53 UTCEchelonGraph re-scored
  69. 2026-10-17 19:53 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  70. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  71. 2026-10-16 21:14 UTCEchelonGraph re-scored
  72. 2026-10-16 21:14 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8
  73. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  74. 2026-10-15 18:10 UTCEchelonGraph re-scored
  75. 2026-10-15 18:09 UTCGHSA enrichmentGHSA-5cvm-3562-3m3m · GitHub CVSS 9.8

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-0634?
CVE-2025-0634 is a critical-severity vulnerability; its CVE record was published on June 30, 2025. Use After Free vulnerability in Samsung Open Source rLottie allows Remote Code Inclusion.This issue affects rLottie: V0.2.
When was the CVE record for CVE-2025-0634 published?
The CVE record for CVE-2025-0634 was published on June 30, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 22, 2026; the record at its source may have been updated since.
Is CVE-2025-0634 actively exploited?
CVE-2025-0634 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-0634?
CVE-2025-0634 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-0634?
A fix for CVE-2025-0634 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-0634

Explore →

Is Your Infrastructure Affected by CVE-2025-0634?

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

Book a Demo →Browse All CVEs