{"id":48693,"date":"2022-09-30T16:24:00","date_gmt":"2022-09-30T16:24:00","guid":{"rendered":"https:\/\/www.darkreading.com\/application-security\/microsoft-confirms-exchange-zero-days-no-patch"},"modified":"2022-09-30T16:24:00","modified_gmt":"2022-09-30T16:24:00","slug":"microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/","title":{"rendered":"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet"},"content":{"rendered":"<div><img decoding=\"async\" src=\"https:\/\/eu-images.contentstack.com\/v3\/assets\/blt66983808af36a8ef\/blt8fcf5db289c785b1\/6196d94d6e8d61565f243a12\/exchange_monticello_shutterstock.jpg\" class=\"ff-og-image-inserted\"><\/div>\n<p>Microsoft is fast-tracking patches for two Exchange Server zero-day vulnerabilities reported overnight, but in the meantime, businesses <a href=\"https:\/\/www.darkreading.com\/dr-tech\/worried-about-the-exchange-0day-here-s-what-to-do\" target=\"_blank\" rel=\"noopener\">should be on the lookout for attacks<\/a>. The computing giant said in a Friday update that it&#8217;s already seeing &#8220;limited targeted attacks&#8221; chaining the bugs together for initial access and takeover of the email system.<\/p>\n<p>The flaws specifically affect on-premises versions of Microsoft Exchange Server 2013, 2016, and 2019 that face the Internet, according to Microsoft. However, it&#8217;s worth noting that security researcher Kevin Beaumont <a href=\"https:\/\/doublepulsar.com\/proxynotshell-the-story-of-the-claimed-zero-day-in-microsoft-exchange-5c63d963a9e9\" target=\"_blank\" rel=\"noopener\">says that<\/a> Microsoft Exchange Online Customers running Exchange hybrid servers with Outlook Web Access (OWA) are also at risk, despite the official advisory stating that Online instances aren&#8217;t impacted. The team at Rapid7 <a href=\"https:\/\/www.rapid7.com\/blog\/post\/2022\/09\/29\/suspected-post-authentication-zero-day-vulnerabilities-in-microsoft-exchange-server\/\" target=\"_blank\" rel=\"noopener\">echoed that assessment<\/a>.<\/p>\n<p>The bugs are tracked as follows:<\/p>\n<ul>\n<li>CVE-2022-41040 (CVSS 8.8), a server-side request forgery (SSRF) vulnerability giving access to any mailbox in Exchange;<\/li>\n<li>CVE-2022-41082 (CVSS 6.3), which allows authenticated remote code execution (RCE) when PowerShell is accessible to the attacker.<\/li>\n<\/ul>\n<p>Importantly, authenticated access to the Exchange Server is necessary for exploitation, Microsoft&#8217;s alert pointed out. Beaumont added, &#8220;Please note exploitation needs valid non-admin credentials for any email user.&#8221;<\/p>\n<h2 class=\"regular-text\">Patches &amp; Mitigations for CVE-2022-41040, CVE-2022-41082<\/h2>\n<p>So far, there&#8217;s no patch available, but Microsoft has triaged the bugs and is fast-tracking a fix.<\/p>\n<p>&#8220;We are working on an accelerated timeline to release a fix,&#8221; according to <a href=\"https:\/\/msrc-blog.microsoft.com\/2022\/09\/29\/customer-guidance-for-reported-zero-day-vulnerabilities-in-microsoft-exchange-server\/\" target=\"_blank\" rel=\"noopener\">Microsoft&#8217;s Friday advisory<\/a>. &#8220;Until then, we&#8217;re providing the mitigations and detections guidance.&#8221;<\/p>\n<p>The mitigations include adding a blocking rule in &#8220;IIS Manager -&gt; Default Web Site -&gt; Autodiscover -&gt; URL Rewrite -&gt; Actions&#8221; to block the known attack patterns; and the company included URL rewrite instructions in the advisory, which it said it &#8220;confirmed are successful in breaking current attack chains.&#8221;<\/p>\n<p>Also, the alert noted that &#8220;since authenticated attackers who can access PowerShell Remoting on vulnerable Exchange systems will be able to trigger RCE using CVE-2022-41082, blocking the ports used for Remote PowerShell can limit the attacks.&#8221;<\/p>\n<h2 class=\"regular-text\">Blindsiding-Bug Disclosure<\/h2>\n<p>The flaws were disclosed in a blog post from Vietnamese security company GTSC, which noted that it submitted bug reports to Trend Micro&#8217;s Zero Day Initiative last month. While typically this would have resulted in a responsible vulnerability disclosure process in which Microsoft would have <a href=\"https:\/\/www.zerodayinitiative.com\/advisories\/disclosure_policy\/\" target=\"_blank\" rel=\"noopener\">120 days to patch<\/a> before the findings were made public, GTSC decided to publish after seeing in-the-wild attacks, it said.<\/p>\n<p>&#8220;After careful testing, we confirmed that those systems were being attacked using this 0-day vulnerability,&#8221; GTSC researchers noted in <a href=\"https:\/\/www.gteltsc.vn\/blog\/warning-new-attack-campaign-utilized-a-new-0day-rce-vulnerability-on-microsoft-exchange-server-12715.html\" target=\"_blank\" rel=\"noopener\">its Thursday blog post<\/a>. &#8220;To help the community temporarily stop the attack before an official patch from Microsoft is available, we publish this article aiming to those organizations who are using Microsoft Exchange email system.&#8221;<\/p>\n<p>It also offered detail analysis of the bug chain, which is similar under the hood to the <a href=\"https:\/\/www.darkreading.com\/attacks-breaches\/cisa-warns-of-ongoing-attacks-targeting-proxyshell-vulnerabilities\" target=\"_blank\" rel=\"noopener\">ProxyShell group of Exchange Server vulnerabilities<\/a>. This prompted Beaumont (@gossithedog) to dub the chain &#8220;ProxyNotShell,&#8221; <a href=\"https:\/\/twitter.com\/GossiTheDog\/status\/1575762721353916417\" target=\"_blank\" rel=\"noopener\">complete with its own logo<\/a>.<\/p>\n<p>He said in his analysis on Friday that while many attributes of the bugs are exactly like ProxyShell, the ProxyShell patches don&#8217;t fix the issue. He also noted that in terms of attack surface, &#8220;near a quarter of a million vulnerable Exchange servers face the internet, give or take.&#8221;<\/p>\n<p>He characterized the situation as &#8220;pretty risky&#8221; in a <a href=\"https:\/\/twitter.com\/GossiTheDog\/status\/1575764727476629505\" target=\"_blank\" rel=\"noopener\">Twitter feed<\/a>, noting that exploitation seems to have been going on for at least a month, and that now that the flaws are public, things could &#8220;go south pretty quickly.&#8221; He also called into question Microsoft&#8217;s mitigation guidance.<\/p>\n<p>&#8220;My guidance would be to stop representing OWA to the internet until there is a patch, unless you want to go down the mitigation route &#8230; but that has been known about for a year, and, eh \u2014 there&#8217;s other ways to exploit Exchange for RCE without PowerShell,&#8221; Beaumont tweeted. &#8220;For example, if you have SSRF (CVE-2022-41040) you are god in Exchange, and can access any mailbox via EWS \u2014 see the prior activity. So, I&#8217;m not sure that mitigation will hold.&#8221;<\/p>\n<p>Microsoft did not immediately respond to a request for comment by Dark Reading.<\/p>\n<p>Read More <a href=\"https:\/\/www.darkreading.com\/application-security\/microsoft-confirms-exchange-zero-days-no-patch\">HERE<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The &#8220;ProxyNotShell&#8221; security vulnerabilities can be chained for remote code execution and total takeover of corporate email platforms.Read More <a href=\"https:\/\/www.darkreading.com\/application-security\/microsoft-confirms-exchange-zero-days-no-patch\">HERE<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_layout":"default_layout","footnotes":""},"categories":[151],"tags":[],"class_list":["post-48693","post","type-post","status-publish","format-standard","hentry","category-darkreading-ti"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.1 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet 2026 | ThreatsHub Cybersecurity News<\/title>\n<meta name=\"description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet 2026 | ThreatsHub Cybersecurity News\" \/>\n<meta property=\"og:description\" content=\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security &amp; Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/\" \/>\n<meta property=\"og:site_name\" content=\"ThreatsHub Cybersecurity News\" \/>\n<meta property=\"article:published_time\" content=\"2022-09-30T16:24:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/eu-images.contentstack.com\/v3\/assets\/blt66983808af36a8ef\/blt8fcf5db289c785b1\/6196d94d6e8d61565f243a12\/exchange_monticello_shutterstock.jpg\" \/>\n<meta name=\"author\" content=\"TH Author\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@threatshub\" \/>\n<meta name=\"twitter:site\" content=\"@threatshub\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"TH Author\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/\"},\"author\":{\"name\":\"TH Author\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\"},\"headline\":\"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet\",\"datePublished\":\"2022-09-30T16:24:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/\"},\"wordCount\":693,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/eu-images.contentstack.com\\\/v3\\\/assets\\\/blt66983808af36a8ef\\\/blt8fcf5db289c785b1\\\/6196d94d6e8d61565f243a12\\\/exchange_monticello_shutterstock.jpg\",\"articleSection\":[\"DarkReading |TI\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/\",\"name\":\"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet 2026 | ThreatsHub Cybersecurity News\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/eu-images.contentstack.com\\\/v3\\\/assets\\\/blt66983808af36a8ef\\\/blt8fcf5db289c785b1\\\/6196d94d6e8d61565f243a12\\\/exchange_monticello_shutterstock.jpg\",\"datePublished\":\"2022-09-30T16:24:00+00:00\",\"description\":\"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#primaryimage\",\"url\":\"https:\\\/\\\/eu-images.contentstack.com\\\/v3\\\/assets\\\/blt66983808af36a8ef\\\/blt8fcf5db289c785b1\\\/6196d94d6e8d61565f243a12\\\/exchange_monticello_shutterstock.jpg\",\"contentUrl\":\"https:\\\/\\\/eu-images.contentstack.com\\\/v3\\\/assets\\\/blt66983808af36a8ef\\\/blt8fcf5db289c785b1\\\/6196d94d6e8d61565f243a12\\\/exchange_monticello_shutterstock.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"name\":\"ThreatsHub Cybersecurity News\",\"description\":\"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\"},\"alternateName\":\"Threatshub.org\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#organization\",\"name\":\"ThreatsHub.org\",\"alternateName\":\"Threatshub.org\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"contentUrl\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/05\\\/Threatshub_Favicon1.jpg\",\"width\":432,\"height\":435,\"caption\":\"ThreatsHub.org\"},\"image\":{\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/x.com\\\/threatshub\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.threatshub.org\\\/blog\\\/#\\\/schema\\\/person\\\/12e0a8671ff89a863584f193e7062476\",\"name\":\"TH Author\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g\",\"caption\":\"TH Author\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet 2026 | ThreatsHub Cybersecurity News","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/","og_locale":"en_US","og_type":"article","og_title":"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet 2026 | ThreatsHub Cybersecurity News","og_description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","og_url":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/","og_site_name":"ThreatsHub Cybersecurity News","article_published_time":"2022-09-30T16:24:00+00:00","og_image":[{"url":"https:\/\/eu-images.contentstack.com\/v3\/assets\/blt66983808af36a8ef\/blt8fcf5db289c785b1\/6196d94d6e8d61565f243a12\/exchange_monticello_shutterstock.jpg","type":"","width":"","height":""}],"author":"TH Author","twitter_card":"summary_large_image","twitter_creator":"@threatshub","twitter_site":"@threatshub","twitter_misc":{"Written by":"TH Author","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#article","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/"},"author":{"name":"TH Author","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476"},"headline":"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet","datePublished":"2022-09-30T16:24:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/"},"wordCount":693,"commentCount":0,"publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#primaryimage"},"thumbnailUrl":"https:\/\/eu-images.contentstack.com\/v3\/assets\/blt66983808af36a8ef\/blt8fcf5db289c785b1\/6196d94d6e8d61565f243a12\/exchange_monticello_shutterstock.jpg","articleSection":["DarkReading |TI"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/","url":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/","name":"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet 2026 | ThreatsHub Cybersecurity News","isPartOf":{"@id":"https:\/\/www.threatshub.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#primaryimage"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#primaryimage"},"thumbnailUrl":"https:\/\/eu-images.contentstack.com\/v3\/assets\/blt66983808af36a8ef\/blt8fcf5db289c785b1\/6196d94d6e8d61565f243a12\/exchange_monticello_shutterstock.jpg","datePublished":"2022-09-30T16:24:00+00:00","description":"ThreatsHub Cybersecurity News | ThreatsHub.org | Cloud Security & Cyber Threats Analysis Hub. 100% Free OSINT Threat Intelligent and Cybersecurity News.","breadcrumb":{"@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#primaryimage","url":"https:\/\/eu-images.contentstack.com\/v3\/assets\/blt66983808af36a8ef\/blt8fcf5db289c785b1\/6196d94d6e8d61565f243a12\/exchange_monticello_shutterstock.jpg","contentUrl":"https:\/\/eu-images.contentstack.com\/v3\/assets\/blt66983808af36a8ef\/blt8fcf5db289c785b1\/6196d94d6e8d61565f243a12\/exchange_monticello_shutterstock.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/www.threatshub.org\/blog\/microsoft-confirms-pair-of-blindsiding-exchange-zero-days-no-patch-yet\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.threatshub.org\/blog\/"},{"@type":"ListItem","position":2,"name":"Microsoft Confirms Pair of Blindsiding Exchange Zero-Days, No Patch Yet"}]},{"@type":"WebSite","@id":"https:\/\/www.threatshub.org\/blog\/#website","url":"https:\/\/www.threatshub.org\/blog\/","name":"ThreatsHub Cybersecurity News","description":"%%focuskw%% Threat Intel \u2013 Threat Intel Services \u2013 CyberIntelligence \u2013 Cyber Threat Intelligence - Threat Intelligence Feeds - Threat Intelligence Reports - CyberSecurity Report \u2013 Cyber Security PDF \u2013 Cybersecurity Trends - Cloud Sandbox \u2013- Threat IntelligencePortal \u2013 Incident Response \u2013 Threat Hunting \u2013 IOC - Yara - Security Operations Center \u2013 SecurityOperation Center \u2013 Security SOC \u2013 SOC Services - Advanced Threat - Threat Detection - TargetedAttack \u2013 APT \u2013 Anti-APT \u2013 Advanced Protection \u2013 Cyber Security Services \u2013 Cybersecurity Services -Threat Intelligence Platform","publisher":{"@id":"https:\/\/www.threatshub.org\/blog\/#organization"},"alternateName":"Threatshub.org","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.threatshub.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.threatshub.org\/blog\/#organization","name":"ThreatsHub.org","alternateName":"Threatshub.org","url":"https:\/\/www.threatshub.org\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","contentUrl":"https:\/\/www.threatshub.org\/blog\/coredata\/uploads\/2025\/05\/Threatshub_Favicon1.jpg","width":432,"height":435,"caption":"ThreatsHub.org"},"image":{"@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/threatshub"]},{"@type":"Person","@id":"https:\/\/www.threatshub.org\/blog\/#\/schema\/person\/12e0a8671ff89a863584f193e7062476","name":"TH Author","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/066276f086d5155df79c850206a779ad368418a844da0182ce43f9cd5b506c3d?s=96&d=mm&r=g","caption":"TH Author"}}]}},"_links":{"self":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/48693","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/comments?post=48693"}],"version-history":[{"count":0,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/posts\/48693\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/media?parent=48693"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/categories?post=48693"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.threatshub.org\/blog\/wp-json\/wp\/v2\/tags?post=48693"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}