Memory disclosure and interruption via unchecked DLS loops
Published Sep 18, 2026 · Updated Sep 18, 2026
Out-of-bounds reads in FluidSynth 2.5.0 through 2.5.5 allow local users to disclose memory or interrupt audio rendering via DLS files. The native DLS loader copies file-controlled wsmp.loop_start and wsmp.loop_length into sample loop points without validating or sanitizing them, permitting loops beyond the sample buffer. Exposure requires a build with enable-native-dls enabled and processing of a crafted DLS file; rendering can read adjacent memory or deny service.
Summary
What happened
Out-of-bounds reads in FluidSynth 2.5.0 through 2.5.5 allow local users to disclose memory or interrupt audio rendering via DLS files. The native DLS loader copies file-controlled wsmp.loop_start and wsmp.loop_length into sample loop points without validating or sanitizing them, permitting loops beyond the sample buffer. Exposure requires a build with enable-native-dls enabled and processing of a crafted DLS file; rendering can read adjacent memory or deny service.
The record
- CVE
- CVE-2026-61721
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- FluidSynth
- Product
- FluidSynth
- Classifications
- CWE-122, CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.5.0, < 2.5.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started