CVE-2026-22853
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 · uneditedFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.20.1, RDPEAR’s NDR array reader does not perform bounds checking on the on‑wire element count and can write past the heap buffer allocated from hints, causing a heap buffer overflow in ndr_read_uint8Array. This vulnerability is fixed in 3.20.1.
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 confidenceFreeRDP contains a heap buffer overflow vulnerability in the RDPEAR NDR array reader. The ndr_read_uint8Array function fails to validate the element count received from the network before allocating and writing data to the heap buffer, allowing an attacker to write past allocated boundaries by sending specially crafted RDP messages with oversized element counts.
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< 3.20.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check FreeRDP client versionRun 'freerdp-version' or 'xfreerdp /version' to obtain the installed FreeRDP version. On Linux, also check package manager output (dpkg -l freerdp or rpm -qa freerdp).Affected if The version is lower than 3.20.1 (e.g., 3.19.x, 3.18.x, 2.x series, or any version string that does not start with 3.20.1 or higher).
-
Identify FreeRDP client usageCheck for running FreeRDP client processes (xfreerdp, wfreerdp, or the freerdp executable) or active RDP sessions originating from FreeRDP clients using process monitoring tools (ps, tasklist, or similar).Affected if FreeRDP client is actively used to connect to RDP servers, as the vulnerability is triggered during the server-to-client NDR data processing.
-
Confirm RDPEAR protocol usageInspect network captures or RDP session logs for RDPEAR (Remote Desktop Protocol Extension for Access Rights) traffic, which occurs during authentication and session initialization. This is typically present in most RDP connections.Affected if RDP sessions are established with servers that send RDPEAR data, as the ndr_read_uint8Array function processes this data.
-
Assess server trust boundaryEvaluate whether FreeRDP clients connect only to trusted/internal RDP servers or may connect to untrusted/external servers. Check RDP connection configurations, saved connection profiles, or connection history.Affected if FreeRDP clients connect to untrusted or externally-accessible RDP servers, as the vulnerability is exploited by a malicious server sending specially crafted NDR array data.
The environment is affected if FreeRDP version is below 3.20.1 AND FreeRDP clients are used to connect to RDP servers (particularly untrusted ones), since the heap overflow occurs when processing RDPEAR NDR array data sent by the server.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.20.1
Upgrade FreeRDP to version 3.20.1 or later. For systems where upgrading is not immediately feasible, restrict RDP access to trusted networks or implement network-level filtering to limit exposure to untrusted RDP connections.
FreeRDP 3.20.1
- Obtain FreeRDP version 3.20.1 or later from the official FreeRDP repository or your distribution's package manager
- Verify the current installed version of FreeRDP to confirm it is below 3.20.1
- Upgrade FreeRDP to version 3.20.1 or newer using your system's package management tools
- Restart any FreeRDP-related services or applications if applicable
- Verify the installed version is now 3.20.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22853 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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