How severe is GHSA-m7g5-gw57-cwcr?

No CVSS score has been assigned to GHSA-m7g5-gw57-cwcr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m7g5-gw57-cwcr?

Affected package information for GHSA-m7g5-gw57-cwcr is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-m7g5-gw57-cwcr?

Upgrade the affected component to the fixed release for GHSA-m7g5-gw57-cwcr, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-m7g5-gw57-cwcr in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-m7g5-gw57-cwcr if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-m7g5-gw57-cwcr actively exploited in the wild?

No public exploit code has been indexed for GHSA-m7g5-gw57-cwcr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m7g5-gw57-cwcr?

GHSA-m7g5-gw57-cwcr has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m7g5-gw57-cwcr?

GHSA-m7g5-gw57-cwcr is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m7g5-gw57-cwcr published, and has it been updated?

GHSA-m7g5-gw57-cwcr was published on October 14, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

FreeRDP before 3.32.0 Unbounded Memory Retention via…

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m7g5-gw57-cwcr.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

FreeRDP from 3.0.0-beta1 before 3.32.0 fails to enforce cumulative or absolute size limits when reassembling RDPDR channel fragments in the proxy. Attackers can send a FIRST fragment followed by continuation fragments without LAST, growing per-session heap streams proportional to traffic and exhausting proxy memory.

Affected Products

1 product · 1 configurations

Application

freerdpfreerdp

≥ 3.0.0 && < 3.32.0

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-m7g5-gw57-cwcr, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is rated as Moderate severity because exploitation requires an established session with device redirection and a proxy explicitly configured to intercept RDPDR channel traffic, resulting in resource exhaustion without compromising data integrity, confidentiality, or allowing arbitrary code…

Workaround published by Red Hat

Limit FreeRDP process resources with ulimit/cgroup controls to contain memory exhaustion. Restrict clients/servers to trusted peers.

Source: Red Hat security advisory for GHSA-m7g5-gw57-cwcr (CC BY 4.0)

Frequently Asked Questions

FreeRDP from 3.0.0-beta1 before 3.32.0 fails to enforce cumulative or absolute size limits when reassembling RDPDR channel fragments in the proxy. Attackers can send a FIRST fragment followed by continuation fragments without LAST, growing per-session heap streams proportional to traffic and exhausting proxy memory.

O3 Security · Impact-Aware SCA

Is GHSA-m7g5-gw57-cwcr in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

FreeRDP before 3.32.0 Unbounded Memory Retention via RDPDR ProxyGHSA-m7g5-gw57-cwcr