Quick answers
- Is CVE-2026-111381 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111381 being exploited in the wild.
- How severe is CVE-2026-111381?
- High severity, with a CVSS score of 7.3, published 16 October 2026.
- Which products and versions are affected?
- FreeRDP Project FreeRDP before 3.32.0.
- Is there a fix for CVE-2026-111381?
- Yes: fixed in 3.32.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111381 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-111381?
- Check whether you run FreeRDP Project FreeRDP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.32.0
Technical details
An integer wraparound in the bitmap size calculation within persistent_cache_read_entry_v2 causes mismatched buffer size accounting. When an attacker crafts a malicious persistent cache v2 file with oversized width and height values, the 64-bit multiplication overflows, producing a small falsified size value that bypasses validation checks. The code then reads a fixed 16 KiB block into a buffer while tracking an incorrect size, leading to heap corruption and potential code execution. Attack requires local file access and user interaction to load the malicious cache file.
Affected products
- FreeRDP Project FreeRDP before 3.32.0
Timeline
- 2026-10-01: disclosed
- 2026-10-16: advisory