meltytech CVE Vulnerabilities & Metrics

Focus on meltytech vulnerabilities and metrics.

Last updated: 16 Jan 2026, 23:25 UTC

About meltytech Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with meltytech. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total meltytech CVEs: 2
Earliest CVE date: 22 Sep 2020, 12:15 UTC
Latest CVE date: 16 Dec 2025, 20:15 UTC

Latest CVE reference: CVE-2025-65834

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 1

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): -100.0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): -100.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical meltytech CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 2.15

Max CVSS: 4.3

Critical CVEs (≥9): 0

CVSS Range vs. Count

Range Count
0.0-3.9 1
4.0-6.9 1
7.0-8.9 0
9.0-10.0 0

CVSS Distribution Chart

Top 5 Highest CVSS meltytech CVEs

These are the five CVEs with the highest CVSS scores for meltytech, sorted by severity first and recency.

All CVEs for meltytech

CVE-2025-65834 meltytech vulnerability CVSS: 0 16 Dec 2025, 20:15 UTC

Meltytech Shotcut 25.10.31 is vulnerable to Buffer Overflow. A memory access violation occurs when processing MLT project files with manipulated width and height parameters. By setting these values to extremely large numbers, the application attempts to allocate excessive memory during image processing, triggering a buffer overflow in the mlt_image_fill_white function.

CVE-2020-24619 meltytech vulnerability CVSS: 4.3 22 Sep 2020, 12:15 UTC

In mainwindow.cpp in Shotcut before 20.09.13, the upgrade check misuses TLS because of setPeerVerifyMode(QSslSocket::VerifyNone). A man-in-the-middle attacker could offer a spoofed download resource.