dbcve.org
FreerdpApplication

CVE-2026-57156

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 3.28.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.28.0 on 32-bit builds, FreeRDP clients contain an integer overflow in update_read_delta_points in libfreerdp/core/orders.c when multiplying an attacker-controlled point count by sizeof(DELTA_POINT), allowing a malicious RDP peer to allocate an undersized heap buffer and then write beyond it during initialization. This issue is fixed in version 3.28.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

FreeRDP clients prior to 3.28.0 on 32-bit builds contain an integer overflow vulnerability in the update_read_delta_points function in libfreerdp/core/orders.c. An attacker-controlled point count multiplied by sizeof(DELTA_POINT) can overflow, causing allocation of an undersized heap buffer. Subsequent initialization writes beyond this buffer boundary, enabling heap corruption.

MitigationUpgrade FreeRDP to version 3.28.0 or later. As a critical RCE-capable vulnerability with network exposure, prioritize patching affected 32-bit client installations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreerdpApplication
Affected:< 3.28.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FreeRDP client version
    Run 'xfreerdp --version' or 'freerdp-version' command, or check package manager: 'dpkg -l freerdp' or 'rpm -qi freerdp'. For library version, check libfreerdp-core.so or similar in /usr/lib/
    Affected if Version is present and less than 3.28.0 (e.g., 3.27.0, 3.0.x, 2.x series)
  2. Identify FreeRDP binary architecture
    Run 'file $(which xfreerdp)' or 'file /usr/lib/x86_64-linux-gnu/freerdp/*.so' to determine if the binary/library is 32-bit (i386/i686) or 64-bit (x86_64). On 32-bit systems, check with 'uname -m'
    Affected if The FreeRDP client binary or libraries are compiled as 32-bit (i386, i686, or 32-bit ARM)
  3. Verify vulnerable library exists
    Locate libfreerdp-core.so in the system: 'find /usr -name 'libfreerdp-core.so*' 2>/dev/null'. Check its version with 'strings libfreerdp-core.so | grep -i version' or 'ldd' to confirm it's the affected component
    Affected if libfreerdp-core.so exists and is from a FreeRDP version below 3.28.0
  4. Confirm RDP client exposure
    Check if FreeRDP client is listening or can accept connections: 'netstat -an | grep 3389' or verify the client binary accepts inbound connections (some FreeRDP configurations can act as gateway)
    Affected if FreeRDP is configured to accept remote connections or is exposed to untrusted networks

The system is affected if it runs a FreeRDP client version below 3.28.0 on a 32-bit architecture and processes RDP data from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.28.0 or later
Fixed in 3.28.0
Vendor patch github.com →
Interim mitigation

Upgrade FreeRDP to version 3.28.0 or later. As a critical RCE-capable vulnerability with network exposure, prioritize patching affected 32-bit client installations.

Recommended fix High confidence

FreeRDP version 3.28.0 or later

  1. 1. Identify all systems running FreeRDP clients or servers with versions prior to 3.28.0
  2. 2. For Linux systems using package managers (apt, yum, dnf), check for available updates: apt update && apt list --upgradable (or equivalent)
  3. 3. Upgrade FreeRDP to version 3.28.0 or later using your package manager: apt install freerdp (or yum install freerdp, etc.)
  4. 4. If using source compilation, clone the FreeRDP repository: git clone https://github.com/FreeRDP/FreeRDP.git
  5. 5. Checkout version 3.28.0: git checkout 3.28.0
  6. 6. Follow the build instructions in the FreeRDP documentation to compile and install the updated version
  7. 7. Verify the installed version matches or exceeds 3.28.0: freerdp-version or check via package manager
  8. 8. Test RDP connectivity to ensure the upgrade does not break legitimate connections
Caveat Minor: Verify compatibility with your RDP server versions after upgrade; some legacy RDP features may have been deprecated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Freerdp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57156 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57156 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data