Microsoft fixes 200 vulnerabilities, including an Outlook flaw CISA confirms is being exploited
Microsoft has released patches for 200 vulnerabilities across Windows, Office, SharePoint, SQL Server, Exchange, its developer tools and several cloud services. One of them, CVE-2026-124194 in Outlook, is already being exploited according to CISA, and 21 others are rated critical.
What happened
CISA, the US cybersecurity agency, today added CVE-2026-124194 to its KEV catalogue of known exploited vulnerabilities, confirming that attackers are already using it. The flaw affects Microsoft Outlook and carries a CVSS score of 6.5: the program fails to warn users about unsafe actions, allowing an unauthenticated attacker to spoof content over a network. It requires the victim to interact, and its main impact is the exposure of information.
The flaw is part of a batch of 200 vulnerabilities Microsoft fixed on 10 November 2026. According to advisories from the Microsoft Security Response Center (MSRC), 21 are rated critical (CVSS 9.0 to 9.9), 178 are rated high (CVSS 8.8) and the Outlook flaw is rated medium. All data comes from the vendor; NVD, the US National Vulnerability Database, has not yet published these entries.
Exploitation status
Only CVE-2026-124194 has confirmed active exploitation. CISA has set 24 November 2026 as the fix deadline for US federal agencies, and it is not known whether the flaw has been used in ransomware campaigns. No public exploit is known, and three specialist outlets have covered the flaw over the past week.
There is no evidence of exploitation or public exploits for the rest, although several of the critical flaws can be attacked over the network without credentials or user interaction, which makes them attractive targets.
The most serious flaws
The critical vulnerabilities are concentrated in Windows network services, SharePoint, SQL Server, and cloud and developer services. The product tags on these entries are machine-inferred, so the reference point is the description in each Microsoft advisory.
- Windows network services, CVSS 9.8 and exploitable without authentication: remote code execution (RCE) in Windows DNS (CVE-2026-88218), Windows DHCP Server (CVE-2026-88243), LDAP, the directory access protocol (CVE-2026-119958), iSCSI, the network storage protocol (CVE-2026-88234) and the Windows Search component (CVE-2026-116928); plus an authentication bypass in Windows Kerberos that allows privilege escalation (CVE-2026-85844).
- Windows multimedia components, CVSS 9.8: buffer overflows in DirectMusic (CVE-2026-95882 and CVE-2026-95901) and Media Foundation (CVE-2026-96157) that allow arbitrary code execution.
- Xbox, CVSS 9.8: RCE in Xbox (CVE-2026-66801) and in the Windows Xbox Live Networking Service (CVE-2026-112967).
- SQL Server, CVSS 9.8: a heap-based buffer overflow that lets an unauthenticated attacker run code (CVE-2026-116945).
- SharePoint: privilege escalation through incorrect authorisation, CVSS 9.9 (CVE-2026-120002); two cross-site scripting (XSS) flaws, CVSS 9.0 (CVE-2026-109454 and CVE-2026-80095); and two deserialisation flaws, CVSS 8.8, that let an authenticated user run code (CVE-2026-109464 and CVE-2026-109472).
- Cloud and development: RCE in Azure DevOps, CVSS 9.9 (CVE-2026-109467); unauthenticated privilege escalation in Azure Managed Grafana (CVE-2026-114160) and Azure OpenAI (CVE-2026-119990), both CVSS 9.8; code injection in Visual Studio Code, CVSS 9.6 (CVE-2026-120779); and privilege escalation in Microsoft Graph, CVSS 9.1 (CVE-2026-114162), and ASP.NET Core, CVSS 9.0 (CVE-2026-114146).
- Other Windows flaws rated CVSS 8.8: iSCSI (CVE-2026-105518), Windows Storage (CVE-2026-105534), NTFS (CVE-2026-105542), Windows DNS (CVE-2026-109463), Remote Desktop Services (CVE-2026-108401) and a local privilege escalation in Desktop Window Manager (CVE-2026-105581).
Full list by product
The remaining vulnerabilities are all rated CVSS 8.8. Most are memory-safety bugs in Office (heap and stack buffer overflows, use-after-free, out-of-bounds reads and double frees) that allow code execution.
- Word: CVE-2026-109501, CVE-2026-109503, CVE-2026-109505, CVE-2026-110047, CVE-2026-110048, CVE-2026-110050, CVE-2026-110054, CVE-2026-110055, CVE-2026-110061, CVE-2026-110062, CVE-2026-110064, CVE-2026-110067, CVE-2026-111285, CVE-2026-111290, CVE-2026-111294, CVE-2026-111295, CVE-2026-111298, CVE-2026-111299, CVE-2026-111304, CVE-2026-111306, CVE-2026-111307, CVE-2026-111308, CVE-2026-111310, CVE-2026-112714, CVE-2026-112715, CVE-2026-112716, CVE-2026-112717, CVE-2026-112718, CVE-2026-112719, CVE-2026-112721, CVE-2026-112722, CVE-2026-112723, CVE-2026-112724, CVE-2026-112726, CVE-2026-112728, CVE-2026-112729, CVE-2026-112730, CVE-2026-112733, CVE-2026-112735, CVE-2026-112739, CVE-2026-112741, CVE-2026-116719, CVE-2026-116720, CVE-2026-116722, CVE-2026-116923, CVE-2026-116925, CVE-2026-123394.
- Excel: CVE-2026-116927, CVE-2026-118292, CVE-2026-118293, CVE-2026-118294, CVE-2026-118295, CVE-2026-118296, CVE-2026-118297, CVE-2026-118298, CVE-2026-118299, CVE-2026-118302, CVE-2026-118700, CVE-2026-118701, CVE-2026-118702, CVE-2026-118703, CVE-2026-118704, CVE-2026-118705, CVE-2026-118706, CVE-2026-118707, CVE-2026-118708, CVE-2026-118709, CVE-2026-118710, CVE-2026-118711, CVE-2026-118712, CVE-2026-118713, CVE-2026-118714, CVE-2026-118715, CVE-2026-118716, CVE-2026-118717, CVE-2026-118718, CVE-2026-118719, CVE-2026-118720, CVE-2026-118721, CVE-2026-118722, CVE-2026-118724, CVE-2026-118725, CVE-2026-118726, CVE-2026-118729, CVE-2026-118730, CVE-2026-118731, CVE-2026-118732, CVE-2026-119986, CVE-2026-120785, CVE-2026-120786, CVE-2026-120788, CVE-2026-120789, CVE-2026-120790, CVE-2026-120791, CVE-2026-123385, CVE-2026-124174, CVE-2026-124176, CVE-2026-124187.
- Outlook: CVE-2026-110043, CVE-2026-110068, CVE-2026-111309, CVE-2026-123375, CVE-2026-123376, CVE-2026-123377, CVE-2026-123380, CVE-2026-123381, CVE-2026-123382, CVE-2026-123383, CVE-2026-123384.
- Access: CVE-2026-109493, CVE-2026-110058, CVE-2026-110059, CVE-2026-110060, CVE-2026-111301, CVE-2026-111305; Visio: CVE-2026-109494, CVE-2026-109496; PowerPoint: CVE-2026-112734, CVE-2026-112737, CVE-2026-120001, CVE-2026-120005; Office: CVE-2026-111289, CVE-2026-116717, CVE-2026-120003, CVE-2026-122198.
- SharePoint (deserialisation, SSRF, type confusion and incorrect authorisation): CVE-2026-109499, CVE-2026-109502, CVE-2026-110044, CVE-2026-123390, CVE-2026-123391.
- SQL Server (SQL injection, command injection and buffer overflows): CVE-2026-116930, CVE-2026-116934, CVE-2026-116941, CVE-2026-116942, CVE-2026-116946, CVE-2026-118105, CVE-2026-118109, CVE-2026-118110, CVE-2026-118120, CVE-2026-67372.
- Exchange Server (code injection, authorisation bypass and input validation): CVE-2026-118149, CVE-2026-118150, CVE-2026-118154, CVE-2026-118207; for CVE-2026-118207, the advisory states that the attacker must be authenticated.
- Visual Studio: CVE-2026-114151, CVE-2026-114152, CVE-2026-114158, CVE-2026-114159, CVE-2026-118745; Visual Studio Code: CVE-2026-114171, CVE-2026-119975, CVE-2026-119983, CVE-2026-121663, CVE-2026-121665.
- Windows: DNS Server (CVE-2026-112727), Print Spooler (CVE-2026-112762, CVE-2026-119950), kernel (CVE-2026-112805), DHCP Client (CVE-2026-113863), Codecs Library (CVE-2026-114164), Active Directory Domain Services (CVE-2026-118146), Remote Desktop Client (CVE-2026-119824, CVE-2026-119839, CVE-2026-119934), Input System (CVE-2026-119862, CVE-2026-119916), SMB (CVE-2026-122176) and PowerShell (CVE-2026-124226).
- Other: Microsoft Defender (CVE-2026-122194) and a path traversal flaw in a Microsoft product not specified in the available excerpt (CVE-2026-124228).
What to do
The available data does not list affected or fixed versions; the reference is the MSRC Security Update Guide, which identifies the specific patch for each product.
- Urgently install the Outlook updates that fix CVE-2026-124194, by 24 November at the latest.
- Prioritise Windows servers running DNS, DHCP, LDAP or Kerberos, especially domain controllers, and those using iSCSI.
- Update SharePoint, SQL Server and Exchange Server as soon as possible and check whether they are exposed to the internet; if so, restrict access until the patch is applied.
- Roll out the Office updates (Word, Excel, Outlook, Access, Visio and PowerPoint) to all machines and remind users to be wary of unexpected emails and documents.
- Update Visual Studio, Visual Studio Code and ASP.NET Core-based applications on developer machines.
- For cloud services (Azure DevOps, Azure OpenAI, Azure Managed Grafana and Microsoft Graph), check each CVE advisory to see whether any customer action is required.
Sources
- Microsoft MSRC: CVE-2026-124194 (Outlook)
- Microsoft MSRC: CVE-2026-109467 (Azure DevOps)
- Microsoft MSRC: CVE-2026-120002 (SharePoint)
- Microsoft MSRC: CVE-2026-116945 (SQL Server)
- Microsoft MSRC: CVE-2026-88218 (Windows DNS)
- Microsoft MSRC: CVE-2026-85844 (Windows Kerberos)
- MSRC: CVE-2026-119958 (Windows LDAP)
Affected technologies
Vulnerabilities (377)
| CVE | Severity | Active exploitation | Published | NVD status |
|---|---|---|---|---|
| CVE-2026-124194 | Medium (6.5) | ⚠ Active exploitation | 11/10/2026 | Analyzed |
| CVE-2026-109467 | Critical (9.9) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-120002 | Critical (9.9) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112967 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114160 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116928 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116945 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119958 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119990 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-66801 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-85844 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88218 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88234 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88243 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-95882 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-95901 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96157 | Critical (9.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-120779 | Critical (9.6) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114162 | Critical (9.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109454 | Critical (9) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114146 | Critical (9) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-80095 | Critical (9) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105518 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105534 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105542 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105581 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-108401 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109463 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109464 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109472 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109493 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109494 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109496 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109499 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109501 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109502 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109503 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109505 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110043 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110044 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110047 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110048 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110050 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110054 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110055 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110058 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110059 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110060 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110061 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110062 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110064 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110067 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110068 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111285 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111289 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111290 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111294 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111295 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111298 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111299 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111301 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111304 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111305 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111306 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111307 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111308 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111309 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111310 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112714 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112715 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112716 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112717 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112718 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112719 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112721 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112722 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112723 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112724 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112726 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112727 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112728 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112729 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112730 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112733 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112734 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112735 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112737 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112739 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112741 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112762 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112805 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113863 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114151 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114152 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114158 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114159 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114164 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114171 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116717 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116719 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116720 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116722 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116923 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116925 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116927 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-116930 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116934 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116941 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116942 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116946 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118105 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118109 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118110 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118120 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118146 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118149 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118150 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118154 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118207 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118292 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118293 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118294 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118295 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118296 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118297 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118298 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118299 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118302 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118700 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118701 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118702 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118703 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118704 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118705 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118706 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118707 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118708 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118709 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118710 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118711 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118712 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118713 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118714 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118715 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118716 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118717 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118718 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118719 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118720 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118721 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118722 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118724 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118725 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118726 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118729 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118730 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118731 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118732 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-118745 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119824 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119839 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119862 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119916 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119934 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119950 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119975 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119983 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119986 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-120001 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-120003 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-120005 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-120785 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-120786 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-120788 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-120789 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-120790 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-120791 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-121663 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-121665 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122176 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122194 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122198 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123375 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123376 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123377 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123380 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123381 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123382 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123383 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123384 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123385 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-123390 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123391 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123394 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-124174 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-124176 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-124187 | High (8.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-124226 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-124228 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67372 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67374 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67375 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67387 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67391 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67632 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67637 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-67646 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-70094 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-85923 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88176 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-94511 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-95975 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96002 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96020 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96064 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96164 | High (8.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-102236 | High (8.6) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-121662 | High (8.6) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119985 | High (8.3) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-120780 | High (8.3) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-121664 | High (8.3) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113753 | High (8.2) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119989 | High (8.2) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113862 | High (8.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118106 | High (8.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118737 | High (8.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119961 | High (8.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119962 | High (8.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-66813 | High (8.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109466 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111296 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111297 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118111 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118112 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118113 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118117 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118118 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118119 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122164 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123387 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88187 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88240 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-94513 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96115 | High (8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-100223 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105028 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105528 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-108403 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-108412 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109473 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110049 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110056 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111302 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112752 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112802 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112978 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112981 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113758 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113759 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113848 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113865 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-114170 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118723 | High (7.8) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-119391 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119816 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119817 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119826 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119847 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119853 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119899 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119907 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119917 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119933 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119939 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119941 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119943 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119954 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119997 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-120782 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-121661 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122183 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122984 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122986 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-124225 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-83563 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-85801 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-85929 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88213 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88227 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88230 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-94507 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-94531 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-95988 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96016 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96031 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96052 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96066 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96102 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96103 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96117 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96129 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96162 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96172 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96174 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96175 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-97013 | High (7.8) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105551 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105561 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109487 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109491 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-109500 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110052 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-110053 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111286 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-111287 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113768 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113859 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116706 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116718 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116926 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116929 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116931 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116937 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116938 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116943 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116947 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118108 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118114 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118115 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118153 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118301 | High (7.5) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-119837 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119938 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119948 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119995 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119996 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-121660 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122169 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123378 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123379 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-124170 | High (7.5) | — | 11/10/2026 | Undergoing Analysis |
| CVE-2026-124185 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-124227 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-84010 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88111 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88244 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96077 | High (7.5) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-102230 | High (7.4) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-62903 | High (7.4) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119900 | High (7.3) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119988 | High (7.1) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-103571 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105510 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105522 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-105586 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-112798 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-113762 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-116707 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-118123 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119387 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119388 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119397 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119402 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119403 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119822 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119827 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119873 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119898 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119921 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-119928 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-122170 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-123389 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-70231 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-88228 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-94522 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96051 | High (7) | — | 11/10/2026 | Awaiting Analysis |
| CVE-2026-96969 | High (7) | — | 11/10/2026 | Awaiting Analysis |
Get the alerts
Relevant vulnerabilities, notable ransomware victims, new groups and the weekly bulletin, as soon as they are published.
Written automatically from NVD, CISA KEV and vendor advisory data. Always check affected versions and patches in the vendor's official advisory before acting.