CVE and update status of the FreeBSD ports tree3,627 unaddressed CVEs in 714 portsAll times are CET
CVE details

CVE-2026-121952

FreeRDP before 3.32.2 has an out-of-bounds write in the proxy because rdp_read_bitmap_cache_v2_capability_set rejects only numCellCaches values above 5, yet the bitmap cache v2 cell array is later accessed at fixed indices 0 through 4. A client connecting to the proxy can declare fewer than five cell caches in its Confirm Active, causing heap corruption, heap data leakage to the backend, or a crash.

Score
9.3 critical
Published
2026-11-04
Links
NVD · cve.org · Report wrong data

Matched ports (1)

PortPackageVersionStatusMaintainer
net/freerdpfreerdp2.11.8_1unaddressedvvd@FreeBSD.org

Template for a VuXML entry

Check the content

Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.

Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>freerdp -- FIXME</topic>
    <affects>
      <package>
	<name>freerdp</name>
	<range><lt>3.32.2</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>CVE-2026-121952: FreeRDP before 3.32.2 has an out-of-bounds write in
	  the proxy because rdp_read_bitmap_cache_v2_capability_set rejects
	  only numCellCaches values above 5, yet the bitmap cache v2 cell
	  array is later accessed at fixed indices 0 through 4. A client
	  connecting to the proxy can declare fewer than five cell caches in
	  its Confirm Active, causing heap corruption, heap data leakage to
	  the backend, or a crash.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-121952</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-121952</url>
    </references>
    <dates>
      <discovery>2026-11-04</discovery>
      <entry>2026-11-04</entry>
    </dates>
  </vuln>