Quick answers
- Is CVE-2026-61714 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61714 being exploited in the wild.
- How severe is CVE-2026-61714?
- High severity, with a CVSS score of 7.8, published 18 September 2026.
- Which products and versions are affected?
- FluidSynth 2.2.4 to 2.5.5.
- Is there a fix for CVE-2026-61714?
- A patch was published on 2026-07-04: Fixed in version 2.5.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61714 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-61714?
- Check whether you run FluidSynth at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds heap buffer access occurs in the MIDI player's channel tracking when synth.midi-channels is configured above 16, causing reads and writes to exceed the fixed-size allocation for the _fluid_player_t::channel_isplaying array. The vulnerability is triggered by configuration alone without requiring a crafted MIDI file. The issue is fixed in FluidSynth 2.5.6 through bounds-checking on channel indexing.
Affected products
- FluidSynth FluidSynth 2.2.4 to 2.5.5
Timeline
- 2026-09-18: disclosed
- 2026-07-04: patched: Fixed in version 2.5.6