Heap-based Buffer Overflow Affecting freerdp/freerdp package, versions [2.0.0,3.32.0)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Heap-based Buffer Overflow vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-FREERDPFREERDP-21245930
- published19 Oct 2026
- disclosed15 Oct 2026
- creditKushal Khemka, Mayank Jangid, Kkartik Aggarwal
Introduced: 15 Oct 2026
NewCVE-2026-110837 (opens in a new tab)How to fix?
Upgrade freerdp/freerdp to version 3.32.0 or higher.
Overview
Affected versions of this package are vulnerable to Heap-based Buffer Overflow via freerdp_dsp_decode_mp3 in the non-FFmpeg DSP path, where the right-channel PCM pointer is computed by advancing a short* by buffer_size elements rather than buffer_size bytes. Because buffer_size is calculated as a byte count (2 × channels × samples-per-second) and then used as a short element offset, pcm_r is placed exactly at the end of the heap allocation. A malicious RDP server can send MP3 audio over the rdpsnd channel so that LAME's hip_decode writes right-channel PCM samples past the allocation boundary, crashing the client.
Note: This is only exploitable when the client is built with WITH_LAME=ON and WITH_DSP_FFMPEG=OFF, and the local audio backend does not natively consume the negotiated WAVE_FORMAT_MPEGLAYER3 format, causing FreeRDP to use the DSP fallback path.