Process hang via overflowing stream-capacity growth
Published Feb 25, 2026 · Updated Feb 25, 2026
Integer overflow in FreeRDP before 3.23.0 allows remote attackers to hang a client or server process through stream-capacity growth. The Stream_EnsureCapacity growth loop doubles a preallocated capacity until it reaches the requested size, but overflow resets the value to zero and leaves the loop unable to terminate. Practical exploitation requires a 32-bit build with available physical memory at least SIZE_MAX; the resulting consequence is a persistent process hang.
Summary
What happened
Integer overflow in FreeRDP before 3.23.0 allows remote attackers to hang a client or server process through stream-capacity growth. The Stream_EnsureCapacity growth loop doubles a preallocated capacity until it reaches the requested size, but overflow resets the value to zero and leaves the loop unable to terminate. Practical exploitation requires a 32-bit build with available physical memory at least SIZE_MAX; the resulting consequence is a persistent process hang.
The record
- CVE
- CVE-2026-27951
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- FreeRDP
- Product
- FreeRDP
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.23.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-qcfc-ghxr-h927 trigger procedureproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo