Search Results (1574 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2024-43537 1 Microsoft 16 Windows 10 1809, Windows 10 21h2, Windows 10 21h2 and 13 more 2026-06-09 6.5 Medium
Windows Mobile Broadband Driver Denial of Service Vulnerability
CVE-2024-43535 1 Microsoft 25 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 22 more 2026-06-09 7 High
Windows Kernel-Mode Driver Elevation of Privilege Vulnerability
CVE-2024-43534 1 Microsoft 25 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 22 more 2026-06-09 6.5 Medium
Windows Graphics Component Information Disclosure Vulnerability
CVE-2024-43533 1 Microsoft 12 Remote Desktop, Windows 11 21h2, Windows 11 21h2 and 9 more 2026-06-09 8.8 High
Remote Desktop Client Remote Code Execution Vulnerability
CVE-2024-43532 1 Microsoft 25 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 22 more 2026-06-09 8.8 High
Remote Registry Service Elevation of Privilege Vulnerability
CVE-2024-43529 1 Microsoft 15 Windows 10 21h2, Windows 10 21h2, Windows 10 22h2 and 12 more 2026-06-09 7.3 High
Windows Print Spooler Elevation of Privilege Vulnerability
CVE-2024-43526 1 Microsoft 16 Windows 10 1809, Windows 10 21h2, Windows 10 21h2 and 13 more 2026-06-09 6.8 Medium
Windows Mobile Broadband Driver Remote Code Execution Vulnerability
CVE-2024-43525 1 Microsoft 16 Windows 10 1809, Windows 10 21h2, Windows 10 21h2 and 13 more 2026-06-09 6.8 Medium
Windows Mobile Broadband Driver Remote Code Execution Vulnerability
CVE-2024-43519 1 Microsoft 25 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 22 more 2026-06-09 8.8 High
Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution Vulnerability
CVE-2024-43518 1 Microsoft 25 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 22 more 2026-06-09 8.8 High
Windows Telephony Server Remote Code Execution Vulnerability
CVE-2024-43515 1 Microsoft 25 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 22 more 2026-06-09 7.5 High
Internet Small Computer Systems Interface (iSCSI) Denial of Service Vulnerability
CVE-2024-43513 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2026-06-09 6.4 Medium
BitLocker Security Feature Bypass Vulnerability
CVE-2024-43506 1 Microsoft 24 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 21 more 2026-06-09 7.5 High
BranchCache Denial of Service Vulnerability
CVE-2022-26826 1 Microsoft 13 Windows 10, Windows 10 1607, Windows 10 1809 and 10 more 2026-06-02 7.2 High
Windows DNS Server Remote Code Execution Vulnerability
CVE-2022-26795 1 Microsoft 12 Windows 10, Windows 10 1809, Windows 10 1909 and 9 more 2026-06-02 7.8 High
Windows Print Spooler Elevation of Privilege Vulnerability
CVE-2022-26926 1 Microsoft 23 Windows 10, Windows 10 1507, Windows 10 1607 and 20 more 2026-05-27 7.8 High
Windows Address Book Remote Code Execution Vulnerability
CVE-2024-38250 1 Microsoft 26 365 Copilot, Office, Office Long Term Servicing Channel and 23 more 2026-05-22 7.8 High
Windows Graphics Component Elevation of Privilege Vulnerability
CVE-2023-29335 1 Microsoft 16 365 Apps, Office, Office Long Term Servicing Channel and 13 more 2026-05-19 7.5 High
Microsoft Word Security Feature Bypass Vulnerability
CVE-2022-26934 1 Microsoft 28 365 Apps, Office, Office Long Term Servicing Channel and 25 more 2026-05-19 6.5 Medium
Windows Graphics Component Information Disclosure Vulnerability
CVE-2023-38545 5 Fedoraproject, Haxx, Microsoft and 2 more 19 Fedora, Libcurl, Windows 10 1809 and 16 more 2026-05-12 8.8 High
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.