Back Inews.Zoombangla Outlook zero-day vulnerability exposes NTLMv2 hashes, Microsoft says
Microsoft has patched an Outlook zero-day vulnerability that attackers are already exploiting, the company said in its November 10, 2026 security release. The flaw, tracked as CVE-2026-124194, carries the title Microsoft Outlook Spoofing Vulnerability. Microsoft says it is aware of active exploitation of the bug.
Microsoft rates the flaw Moderate in severity and has given it a CVSS score of 6.5 out of 10. That score is modest for a bug that is already being used in attacks. Security reports have urged administrators to prioritize the fix despite the moderate rating.
According to Microsoft, an unauthenticated attacker can exploit the flaw by sending a specially crafted message file to a target. The attacker must then persuade the user to open that file in Outlook. Microsoft says user interaction is required, so the attack cannot succeed unless the victim opens the file.
Opening the malicious file can cause Outlook to connect to a network location controlled by the attacker. Microsoft says that connection happens without the usual external-content warning Outlook shows. As a result, the user may see no prompt before Outlook reaches out to the attacker’s system.
That connection discloses the user’s NTLMv2 hash to the attacker, according to the company. An attacker holding the hash could use it to authenticate as that user. Microsoft lists the impact of CVE-2026-124194 as spoofing.
The Outlook fix shipped as part of Microsoft’s monthly Patch Tuesday release for November, which covered a very large batch of flaws. Reported totals for the release range from 1,093 to 1,235 flaws. The spread reflects different counting methods, such as whether flaws in the Edge browser and third-party components are included.
The Cybersecurity and Infrastructure Security Agency added CVE-2026-124194 to its Known Exploited Vulnerabilities catalog on November 10, 2026, the same day Microsoft released the fix. The catalog entry lists Microsoft as the vendor and Office as the affected product. It sets a federal remediation due date of November 24, 2026, though some reports describe the deadline as the end of the month.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
