GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration
oesa-2026-1519
Vulnerability from osv_openeuler
Published
2026-03-06 11:10
Modified
2026-08-06 11:10
Summary
freerdp security update
Details

FreeRDP is a client implementation of the Remote Desktop Protocol (RDP) that follows Microsoft's open specifications. This package provides the client applications xfreerdp.

Security Fix(es):

A malicious server can trigger a client-side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-22852)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.20.1, a heap-buffer-overflow occurs in drive read when a server-controlled read length is used to read file data into an IRP output stream buffer without a hard upper bound, allowing an oversized read to overwrite heap memory. This vulnerability is fixed in 3.20.1.(CVE-2026-22854)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.20.1, a heap out-of-bounds read occurs in the smartcard SetAttrib path when the cbAttrLen parameter does not match the actual NDR (Network Data Representation) buffer length. An attacker could potentially exploit this vulnerability to read sensitive information from process memory or cause the application to crash.(CVE-2026-22855)

A malicious server can trigger a client-side use after free, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-22856)

A malicious server can trigger a client-side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout. The vulnerability exists in the irp_thread_func function.(CVE-2026-22857)

A malicious server can trigger a client‑side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-22859)

A heap-based buffer overflow vulnerability exists in FreeRDP within the planar_decompress_plane_rle function, which may lead to memory corruption and arbitrary code execution.(CVE-2026-23530)

FreeRDP is a free implementation of the Remote Desktop Protocol (RDP). Prior to version 3.21.0, a heap buffer overflow vulnerability existed in the ClearCodec component. Specifically, when glyphData is present, the clear_decompress function calls freerdp_image_copy_no_overlap without validating the destination rectangle. This allows for out-of-bounds read/write operations when processing crafted RDPGFX surface updates. A malicious server can exploit this to trigger a client-side heap buffer overflow, causing a crash (Denial of Service) and potential heap corruption. Depending on allocator behavior and surrounding heap layout, there is a risk of arbitrary code execution.(CVE-2026-23531)

A heap-buffer-overflow vulnerability exists in FreeRDP software that could allow an attacker to execute arbitrary code or cause denial of service on affected systems. This vulnerability affects the gdi_SurfaceToSurface function and is present in versions 3.20.2 and earlier.(CVE-2026-23532)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, a client-side heap buffer overflow vulnerability exists in the RDPGFX ClearCodec decode path, specifically in the clear_decompress_residual_data function. When processing maliciously crafted residual data, out-of-bounds writes occur during color output. A malicious server can exploit this to trigger a client-side heap buffer overflow, causing a crash (Denial of Service) and potential heap corruption. Depending on allocator behavior and surrounding heap layout, there is a risk of arbitrary code execution.(CVE-2026-23533)

FreeRDP is a free implementation of the Remote Desktop Protocol (RDP). Prior to version 3.21.0, a client-side heap buffer overflow vulnerability exists in the ClearCodec bands decode path. When a malicious server sends crafted band coordinates, it allows writes past the end of the destination surface buffer. This can be exploited to trigger a client-side heap buffer overflow, causing a crash (Denial of Service) and potentially leading to heap corruption with the risk of arbitrary code execution, depending on allocator behavior and surrounding heap layout.(CVE-2026-23534)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, the FastGlyph parsing process trusts cbData/remaining length but never validates it against the minimum size implied by cx/cy. A malicious server can exploit this vulnerability to trigger a client-side global heap buffer overflow, causing a crash and resulting in a denial of service.(CVE-2026-23732)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, the xf_Pointer_New function frees the cursorPixels memory on failure. Subsequently, the pointer_free function calls xf_Pointer_Free, which attempts to free the same memory again, triggering an AddressSanitizer (ASan) detected use-after-free (UAF). A malicious server can trigger a client-side use-after-free, causing a crash (Denial of Service) and potentially leading to heap corruption with a risk of code execution, depending on allocator behavior and surrounding heap layout.(CVE-2026-23883)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, a use-after-free vulnerability exists. Specifically, the deletion of an offscreen bitmap leaves the gdi->drawing pointer referencing freed memory. When subsequent related update packets are processed, this leads to a use-after-free condition. A malicious server can exploit this vulnerability when a client connects, causing a client-side crash (Denial of Service) and potentially leading to heap corruption. Depending on allocator behavior and heap layout, there is a risk of arbitrary code execution.(CVE-2026-23884)

A malicious server can trigger a client‑side heap use after free, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24491)

A malicious server can trigger a client‑side heap use after free, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24675)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.22.0, AUDIN format renegotiation frees the active format list while the capture thread continues using audin->format, leading to a use after free in audio_format_compatible. This vulnerability is fixed in 3.22.0.(CVE-2026-24676)

A malicious server can trigger a client‑side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24679)

A malicious server can trigger a client-side heap use after free, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24681)

A malicious server can trigger a client‑side heap buffer over flow, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24682)

A malicious server can trigger a client‑side heap use after free, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24683)

A malicious server can trigger a client‑side heap use after free, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24684)

This is an out-of-bounds read vulnerability affecting FreeRDP clients. A malicious RDP server can exploit this to:

  1. Information Disclosure: Read sensitive data from the client's heap memory
  2. Denial of Service: Cause client crashes through memory access violations

The attack requires user interaction (connecting to a malicious server), but no authentication is needed on the server side.(CVE-2026-25941)

A malicious server can trigger a client-side heap use after free, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-25997)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, a buffer overread in freerdp_image_copy_from_icon_data() (libfreerdp/codec/color.c) can be triggered by crafted RDP Window Icon (TS_ICON_INFO) data. The bug is reachable over the network when a client processes icon data from an RDP server (or from a man-in-the-middle). Version 3.23.0 fixes the issue.(CVE-2026-26271)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, rail_window_free dereferences a freed xfAppWindow pointer during HashTable_Free cleanup because xf_rail_window_common calls free(appWindow) on title allocation failure without first removing the entry from the railWindows hash table, leaving a dangling pointer that is freed again on disconnect. Version 3.23.0 fixes the vulnerability.(CVE-2026-26986)

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, a missing bounds check in smartcard_unpack_read_size_align() (libfreerdp/utils/smartcard_pack.c:1703) allows a malicious RDP server to crash the FreeRDP client via a reachable WINPR_ASSERT → abort(). The crash occurs in upstream builds where WITH_VERBOSE_WINPR_ASSERT=ON (default in FreeRDP 3.22.0 / current WinPR CMake defaults). Smartcard redirection must be explicitly enabled by the user (e.g., xfreerdp /smartcard; /smartcard-logon implies /smartcard). Version 3.23.0 fixes the issue.(CVE-2026-27015)

Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
References
https://www.openeuler.org/zh/security/security-bu… ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-22852 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-22854 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-22855 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-22856 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-22857 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-22859 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23530 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23531 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23532 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23533 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23534 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23732 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23883 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-23884 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24491 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24675 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24676 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24679 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24681 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24682 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24683 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-24684 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-25941 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-25997 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-26271 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-26986 ADVISORY
https://nvd.nist.gov/vuln/detail/CVE-2026-27015 ADVISORY
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "freerdp-2.11.8-1.oe2003sp4.aarch64.rpm",
          "freerdp-debuginfo-2.11.8-1.oe2003sp4.aarch64.rpm",
          "freerdp-debugsource-2.11.8-1.oe2003sp4.aarch64.rpm",
          "freerdp-devel-2.11.8-1.oe2003sp4.aarch64.rpm",
          "freerdp-help-2.11.8-1.oe2003sp4.aarch64.rpm",
          "libwinpr-2.11.8-1.oe2003sp4.aarch64.rpm",
          "libwinpr-devel-2.11.8-1.oe2003sp4.aarch64.rpm"
        ],
        "src": [
          "freerdp-2.11.8-1.oe2003sp4.src.rpm"
        ],
        "x86_64": [
          "freerdp-2.11.8-1.oe2003sp4.x86_64.rpm",
          "freerdp-debuginfo-2.11.8-1.oe2003sp4.x86_64.rpm",
          "freerdp-debugsource-2.11.8-1.oe2003sp4.x86_64.rpm",
          "freerdp-devel-2.11.8-1.oe2003sp4.x86_64.rpm",
          "freerdp-help-2.11.8-1.oe2003sp4.x86_64.rpm",
          "libwinpr-2.11.8-1.oe2003sp4.x86_64.rpm",
          "libwinpr-devel-2.11.8-1.oe2003sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP4",
        "name": "freerdp",
        "purl": "pkg:rpm/openEuler/freerdp\u0026distro=openEuler-20.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.11.8-1.oe2003sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "Critical"
  },
  "details": "FreeRDP is a client implementation of the Remote Desktop Protocol (RDP) that follows Microsoft\u0026amp;apos;s\nopen specifications. This package provides the client applications xfreerdp.\r\n\r\nSecurity Fix(es):\n\nA malicious server can trigger a client-side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-22852)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.20.1, a heap-buffer-overflow occurs in drive read when a server-controlled read length is used to read file data into an IRP output stream buffer without a hard upper bound, allowing an oversized read to overwrite heap memory. This vulnerability is fixed in 3.20.1.(CVE-2026-22854)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.20.1, a heap out-of-bounds read occurs in the smartcard SetAttrib path when the `cbAttrLen` parameter does not match the actual NDR (Network Data Representation) buffer length. An attacker could potentially exploit this vulnerability to read sensitive information from process memory or cause the application to crash.(CVE-2026-22855)\n\nA malicious server can trigger a client-side use after free, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-22856)\n\nA malicious server can trigger a client-side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout. The vulnerability exists in the irp_thread_func function.(CVE-2026-22857)\n\nA malicious server can trigger a client\u2011side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code\u2011execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-22859)\n\nA heap-based buffer overflow vulnerability exists in FreeRDP within the planar_decompress_plane_rle function, which may lead to memory corruption and arbitrary code execution.(CVE-2026-23530)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol (RDP). Prior to version 3.21.0, a heap buffer overflow vulnerability existed in the ClearCodec component. Specifically, when `glyphData` is present, the `clear_decompress` function calls `freerdp_image_copy_no_overlap` without validating the destination rectangle. This allows for out-of-bounds read/write operations when processing crafted RDPGFX surface updates. A malicious server can exploit this to trigger a client-side heap buffer overflow, causing a crash (Denial of Service) and potential heap corruption. Depending on allocator behavior and surrounding heap layout, there is a risk of arbitrary code execution.(CVE-2026-23531)\n\nA heap-buffer-overflow vulnerability exists in FreeRDP software that could allow an attacker to execute arbitrary code or cause denial of service on affected systems. This vulnerability affects the gdi_SurfaceToSurface function and is present in versions 3.20.2 and earlier.(CVE-2026-23532)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, a client-side heap buffer overflow vulnerability exists in the RDPGFX ClearCodec decode path, specifically in the `clear_decompress_residual_data` function. When processing maliciously crafted residual data, out-of-bounds writes occur during color output. A malicious server can exploit this to trigger a client-side heap buffer overflow, causing a crash (Denial of Service) and potential heap corruption. Depending on allocator behavior and surrounding heap layout, there is a risk of arbitrary code execution.(CVE-2026-23533)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol (RDP). Prior to version 3.21.0, a client-side heap buffer overflow vulnerability exists in the ClearCodec bands decode path. When a malicious server sends crafted band coordinates, it allows writes past the end of the destination surface buffer. This can be exploited to trigger a client-side heap buffer overflow, causing a crash (Denial of Service) and potentially leading to heap corruption with the risk of arbitrary code execution, depending on allocator behavior and surrounding heap layout.(CVE-2026-23534)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, the FastGlyph parsing process trusts `cbData`/remaining length but never validates it against the minimum size implied by `cx`/`cy`. A malicious server can exploit this vulnerability to trigger a client-side global heap buffer overflow, causing a crash and resulting in a denial of service.(CVE-2026-23732)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, the `xf_Pointer_New` function frees the `cursorPixels` memory on failure. Subsequently, the `pointer_free` function calls `xf_Pointer_Free`, which attempts to free the same memory again, triggering an AddressSanitizer (ASan) detected use-after-free (UAF). A malicious server can trigger a client-side use-after-free, causing a crash (Denial of Service) and potentially leading to heap corruption with a risk of code execution, depending on allocator behavior and surrounding heap layout.(CVE-2026-23883)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0, a use-after-free vulnerability exists. Specifically, the deletion of an offscreen bitmap leaves the `gdi-\u0026gt;drawing` pointer referencing freed memory. When subsequent related update packets are processed, this leads to a use-after-free condition. A malicious server can exploit this vulnerability when a client connects, causing a client-side crash (Denial of Service) and potentially leading to heap corruption. Depending on allocator behavior and heap layout, there is a risk of arbitrary code execution.(CVE-2026-23884)\n\nA malicious server can trigger a client\u2011side heap use after free, causing a crash (DoS) and potential heap corruption with code\u2011execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24491)\n\nA malicious server can trigger a client\u2011side heap use after free, causing a crash (DoS) and potential heap corruption with code\u2011execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24675)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.22.0, AUDIN format renegotiation frees the active format list while the capture thread continues using audin-\u0026gt;format, leading to a use after free in audio_format_compatible. This vulnerability is fixed in 3.22.0.(CVE-2026-24676)\n\nA malicious server can trigger a client\u2011side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code\u2011execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24679)\n\nA malicious server can trigger a client-side heap use after free, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24681)\n\nA malicious server can trigger a client\u2011side heap buffer over flow, causing a crash (DoS) and potential heap corruption with code\u2011execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24682)\n\nA malicious server can trigger a client\u2011side heap use after free, causing a crash (DoS) and potential heap corruption with code\u2011execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24683)\n\nA malicious server can trigger a client\u2011side heap use after free, causing a crash (DoS) and potential heap corruption with code\u2011execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-24684)\n\nThis is an out-of-bounds read vulnerability affecting FreeRDP clients. A malicious RDP server can exploit this to:\n\n1. **Information Disclosure**: Read sensitive data from the client\u0026apos;s heap memory\n2. **Denial of Service**: Cause client crashes through memory access violations\n\nThe attack requires user interaction (connecting to a malicious server), but no authentication is needed on the server side.(CVE-2026-25941)\n\nA malicious server can trigger a client-side heap use after free, causing a crash (DoS) and potential heap corruption with code-execution risk depending on allocator behavior and surrounding heap layout.(CVE-2026-25997)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, a buffer overread in `freerdp_image_copy_from_icon_data()` (libfreerdp/codec/color.c) can be triggered by crafted RDP Window Icon (TS_ICON_INFO) data. The bug is reachable over the network when a client processes icon data from an RDP server (or from a man-in-the-middle). Version 3.23.0 fixes the issue.(CVE-2026-26271)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, `rail_window_free` dereferences a freed `xfAppWindow` pointer during `HashTable_Free` cleanup because `xf_rail_window_common` calls `free(appWindow)` on title allocation failure without first removing the entry from the `railWindows` hash table, leaving a dangling pointer that is freed again on disconnect. Version 3.23.0 fixes the vulnerability.(CVE-2026-26986)\n\nFreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.23.0, a missing bounds check in `smartcard_unpack_read_size_align()` (`libfreerdp/utils/smartcard_pack.c:1703`) allows a malicious RDP server to crash the FreeRDP client via a reachable `WINPR_ASSERT` \u2192 `abort()`. The crash occurs in upstream builds where `WITH_VERBOSE_WINPR_ASSERT=ON` (default in FreeRDP 3.22.0 / current WinPR CMake defaults). Smartcard redirection must be explicitly enabled by the user (e.g., `xfreerdp /smartcard`; `/smartcard-logon` implies `/smartcard`). Version 3.23.0 fixes the issue.(CVE-2026-27015)",
  "id": "OESA-2026-1519",
  "modified": "2026-08-06T11:10:31Z",
  "published": "2026-03-06T11:10:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1519"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22852"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22854"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22855"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22856"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22857"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22859"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23530"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23531"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23532"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23533"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23534"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23732"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23883"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23884"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24491"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24675"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24676"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24679"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24681"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24682"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24683"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24684"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25941"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25997"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26271"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-26986"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27015"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "freerdp security update",
  "upstream": [
    "CVE-2026-22852",
    "CVE-2026-22854",
    "CVE-2026-22855",
    "CVE-2026-22856",
    "CVE-2026-22857",
    "CVE-2026-22859",
    "CVE-2026-23530",
    "CVE-2026-23531",
    "CVE-2026-23532",
    "CVE-2026-23533",
    "CVE-2026-23534",
    "CVE-2026-23732",
    "CVE-2026-23883",
    "CVE-2026-23884",
    "CVE-2026-24491",
    "CVE-2026-24675",
    "CVE-2026-24676",
    "CVE-2026-24679",
    "CVE-2026-24681",
    "CVE-2026-24682",
    "CVE-2026-24683",
    "CVE-2026-24684",
    "CVE-2026-25941",
    "CVE-2026-25997",
    "CVE-2026-26271",
    "CVE-2026-26986",
    "CVE-2026-27015"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.


Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.