CVE-2025-65834
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMeltytech 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMeltytech Shotcut 25.10.31 contains a buffer overflow vulnerability in the mlt_image_fill_white function. Attackers can trigger the vulnerability by crafting malicious MLT project files with excessively large width and height parameter values, causing the application to attempt allocating unbounded memory and overflow a buffer during image processing.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 25.10.31CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Shotcut versionLaunch Shotcut and navigate to the About section (typically via Help > About), or run 'shotcut --version' from the command line if availableAffected if The installed version is exactly 25.10.31
-
Locate MLT project files on the systemSearch for files with .mlt or .xml extensions in your project directories, which are the MLT project file formats used by ShotcutAffected if You have MLT project files that could be opened with the affected version
-
Determine if the system processes untrusted MLT filesReview whether you open MLT project files from external sources, shared repositories, or untrusted users that could contain malicious dimension parametersAffected if The affected Shotcut version processes MLT files from untrusted or external sources
-
Check for unusually large image dimensions in MLT filesOpen any MLT project files in a text editor and inspect the width and height attributes within the producer or filter elements for values exceeding reasonable bounds (e.g., values in the millions or beyond typical display resolutions)Affected if Any MLT file contains width or height parameter values that are excessively large (orders of magnitude beyond standard resolutions like 1920x1080 or 4096x2160)
You are affected if running Shotcut version 25.10.31 and open MLT project files that could contain maliciously crafted large width/height parameters, as the buffer overflow occurs during image processing of those files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict validation of width and height parameters from MLT project files before memory allocation operations, ensuring values fall within reasonable bounds. Add integer overflow checks and allocate buffers based on validated dimensions only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65834 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-65834 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data