Stack Buffer Overflow Vulnerability in Musescore3: Risk of Arbitrary Code Execution

musescore3 Updated 02 Oct 2025

Summary

28/03/2023
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2023-26923: Musescore 3.0 to 4.0.1 has a stack buffer overflow vulnerability that occurs when reading misconfigured midi files. Affects musescore3 versions < 3.2.3+dfsg2-18. Fixed in 3.2.3+dfsg2-18. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Musescore3 is a popular open-source music notation software that allows users to create, play, and print sheet music. It supports a variety of file formats and provides advanced features for musicians and composers. However, versions 3.0 to 4.0.1 of Musescore3 are susceptible to a stack buffer overflow vulnerability when processing misconfigured MIDI files, which can lead to severe security risks.

Vulnerability Detail

The vulnerability arises from improper handling of MIDI files, which can be exploited by an attacker to cause a stack buffer overflow. This flaw allows the attacker to execute arbitrary code on the affected system, potentially leading to unauthorized access, data corruption, or system compromise. The issue is particularly critical as it affects a widely used application in the music community, making it a prime target for exploitation.

How To Fix

Minimum fixed version

3.2.3+dfsg2-18

This is the first release that contains the fix.

sudo apt-get install --only-upgrade musescore3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary measure, users can avoid opening MIDI files from untrusted sources or ensure that MIDI files are properly configured before use. This can help mitigate the risk of exploitation until the software is updated.

Conclusion

The stack buffer overflow vulnerability in Musescore3 poses a significant risk to users, allowing for potential arbitrary code execution through misconfigured MIDI files. It is crucial for users to update to the latest patched version to safeguard their systems and data.

See every vulnerability recorded for musescore3 →

Share this vulnerability

FAQ

A stack buffer overflow occurs when a program writes more data to a buffer located on the stack than it can hold, which can overwrite adjacent memory and lead to unpredictable behavior or security vulnerabilities.

If you are using Musescore3 versions between 3.0 and 4.0.1, your installation is vulnerable. Check your version by opening the application and navigating to the 'About' section.

If an immediate update is not possible, refrain from opening MIDI files from unknown or untrusted sources to minimize the risk of exploitation.

Yes, you can use tools like Vulert, which monitors open-source vulnerabilities in your software by analyzing a manifest file like package-lock.json. You can check for vulnerabilities in your application using the Vulert playground without needing to sign up.

Failing to address this vulnerability can lead to unauthorized code execution, data loss, or compromise of the system, putting both the user and their data at risk.

Related vulnerabilities

Recent vulnerabilities recorded for musescore3.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

3.2.3+dfsg2-18

This is the first release that contains the fix.

sudo apt-get install --only-upgrade musescore3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback