← Back to results
Vulnerability record · public intelligence
CVE-2026-27950
HIGH

FreeRDP heap-use-after-free in update_pointer_new(SDL): Fix Applied in the Wrong File

Published Feb 25, 2026 · Updated Oct 23, 2026

Severity · CVSSHIGH · 7.5
Known exploitationNot listed
EPSS / likelihood0.85%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

FreeRDP heap-use-after-free in update_pointer_new(SDL): Fix Applied in the Wrong File

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, the fix for the heap-use-after-free described in CVE-2026-24680 is incomplete. While the vulnerable execution flow referenced in the advisory exists in the SDL2 implementation, the fix appears to have been applied only to the SDL3 code path. In the SDL2 implementation, the pointer is not nulled after free. This creates a situation where the advisory suggests the vulnerability is fully resolved, while builds or environments still using SDL2 may retain the vulnerable logic. A complete fix is available in version 3.23.0.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
MEDIUM
Confidence
10%
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗
  3. Patch commit ↗
  4. Source repository ↗

Record history

Published Feb 25, 2026 · Last refreshed Oct 23, 2026