Bug 2549790 (CVE-2026-109242) - CVE-2026-109242 freerdp: FreeRDP: Denial of Service via uninitialized progressive tile handling
Summary: CVE-2026-109242 freerdp: FreeRDP: Denial of Service via uninitialized progres...
Keywords:
Status: NEW
Alias: CVE-2026-109242
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2561610 2561611 2561609
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-12 16:50 UTC by OSIDB Bzimport
Modified: 2026-11-03 13:55 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:93592 0 None None None 2026-11-02 10:57:17 UTC
Red Hat Product Errata RHSA-2026:94510 0 None None None 2026-11-03 13:55:17 UTC
Red Hat Product Errata RHSA-2026:94514 0 None None None 2026-11-03 13:00:30 UTC

Description OSIDB Bzimport 2026-10-12 16:50:49 UTC 
FreeRDP before 3.0.0 and 3.6.0 before 3.32.0 renders uninitialized heap memory from un-decoded progressive tiles because the tile->current buffer is allocated without zeroing. A malicious RDP server can send a crafted WBT_TILE_FIRST then WBT_TILE_UPGRADE sequence to paint heap bytes onscreen or abort the client process.
Comment 2 Jon Orris 2026-11-02 10:57:17 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:93592 https://access.redhat.com/errata/RHSA-2026:93592
Comment 3 Jon Orris 2026-11-03 13:00:29 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:94514 https://access.redhat.com/errata/RHSA-2026:94514
Comment 4 Jon Orris 2026-11-03 13:55:16 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:94510 https://access.redhat.com/errata/RHSA-2026:94510
Note You need to log in before you can comment on or make changes to this bug.