Microsoft is working to resolve an ongoing Exchange Online issue that has been mistakenly quarantining customers' mailboxes since Sunday. [...]

Microsoft is actively working to resolve an issue within its Exchange Online service that has led to the incorrect quarantining of customer mailboxes since Sunday, July 19. The incident, identified by Microsoft as EX1436407, has resulted in affected users being unable to send or receive emails and experiencing difficulties accessing their calendars.
The company has attributed the problem to a recent infrastructure change. This change reportedly caused an unexpected increase in memory consumption due to indexing data, leading to an out-of-memory condition that subsequently triggered the erroneous mailbox quarantines. Microsoft has confirmed that users sending emails to these quarantined mailboxes may receive Non-delivery Reports (NDRs).
This current issue is a recurrence of a previous incident, tracked under the designation EX1434354, indicating that additional steps are required for a complete resolution. While Microsoft has not specified the geographical regions or the exact number of customers impacted, it has classified the event as an incident, which typically signifies a noticeable effect on users.
Remediation efforts involve an ongoing cleanup of the excessive indexing data. Progress on this cleanup was reported at 66% complete by Wednesday afternoon and had advanced to 72% by Wednesday evening. As memory levels are validated across different regions, mailboxes are gradually being removed from quarantine to expedite recovery.
Microsoft has not yet provided a definitive timeline for the full restoration of services but has indicated that an update with this information would be forthcoming. The next scheduled update on the incident was set for 6 p.m. UTC on the day of the report.
This is not the first time Exchange Online has faced issues involving email quarantines or incorrect spam flagging. In March 2025, an Exchange Online bug caused anti-spam systems to mistakenly quarantine emails. A similar issue occurred in May 2025, when a machine learning model incorrectly flagged emails from Gmail accounts as spam. More recently, in September, an anti-spam service problem blocked Exchange Online and Microsoft Teams users from opening URLs and also led to the mistaken quarantining of emails. In February, Microsoft addressed another Exchange Online issue where faulty heuristic detection rules, intended to block credential phishing, incorrectly flagged thousands of legitimate URLs as phishing links, leading to the quarantine of valid emails.

Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. "Sansec is publishing early

JetBrains is urging Cadence users to revoke and rotate all credentials following a security incident last month in which unidentified threat actors exploited a recently disclosed critical vulnerability in TeamCity to breach its own environment. "Cadence users should immediately revoke or rotate all credentials and secrets that may have been used to run their Cadence executions," JetBrains said.

Broadcom has released security updates for two security flaws impacting VMware Workstation and Fusion, including one critical bug that could result in arbitrary code execution under certain conditions. The vulnerability, tracked as CVE-2026-59346 (CVSS score: 9.3), is an integer-overflow vulnerability that a local attacker with elevated privileges can exploit to run arbitrary code. "A
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
A security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack remotely.
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.