Microsoft Defender Misclassifies Legitimate Google Search Links as Threats
Microsoft is investigating a configuration error in Defender for Office 365 that causes legitimate Google search result links to be treated as threats. Home users, small and medium businesses, and enterprise customers running Microsoft Windows Defender have reported the issue.
When users click the affected links they see the warning “This website may be unsafe.” Copying the URL and pasting it into a browser does not bypass the block. The problem is registered under advisory number MO1465962.
The root cause is an incorrect classification performed by the Safe Links component. Instead of allowing normal Google URLs, the system marks them as malicious and blocks navigation. Safe Links normally protects organizations by rewriting URLs in incoming email and re-evaluating them at click time; the mechanism operates across email, Teams, and other Microsoft 365 applications.
Security teams are also impacted. Administrators receive related alerts and must investigate incidents that appear in the Microsoft Defender Portal and in the Microsoft Sentinel SIEM platform. These alerts consume analyst time without indicating any real phishing campaign.
Microsoft has classified the problem as an advisory, typically indicating limited scope, and is working to correct the faulty classification rules. The company has not yet published details on the number of affected customers or the regions involved.
Related articles
Telegram Desktop Bug Deletes Up to 800 GB of User Data on Windows Due to Spellcheck Library Error
A critical configuration flaw in Telegram Desktop for Windows caused the application to recursively delete the entire contents of the C:\custom directory, resulting in the loss of approximately 800 GB of user data including programs, projects, and personal files. The issue originated in the lib_spellcheck library introduced in version 7.1.0, where an empty working directory path was concatenated with /custom and resolved by Qt into an absolute system path. Instead of locating a dictionary file, the code invoked removeRecursively() on the discovered directory, systematically erasing all accessible files while leaving folder structures intact. The bug affected only Windows builds with the built-in spellchecker enabled and remained in distribution for roughly 66 hours across versions 7.1.0 and 7.1.1. Researchers confirmed the behavior using Process Monitor logs and reported it via ticket #31170, prompting developers to add path validation before the function call and disable dictionary operations on empty paths. The corrected code was released in Telegram Desktop 7.1.2, and users running the vulnerable versions are advised to update immediately. No impact was observed on Linux or macOS platforms.
Essential Active Directory Checks Before Launching Any Penetration Test
Internal penetration tests of Active Directory can quickly generate noise in logs or disrupt services if techniques are applied without proper context. The article stresses that testers must first map domain boundaries, identify controllers, clarify allowed segments, and establish escalation procedures with the client. Detailed inventory of user, service, and privileged accounts is required, including analysis of Kerberos pre-authentication settings that enable AS-REP Roasting. Testers should also examine DACL permissions, delegation relationships, and Active Directory Certificate Services templates before attempting any exploitation. The guidance covers NTLM relay risks, the importance of maintaining an action log, and the distinction between standard pentests and Red Team engagements. A demo version of the Red September course on Active Directory attacks is offered to practice these steps in a controlled environment.
Attackers Exploit Critical Sangoma Switchvox SQL Injection Flaw CVE-2026-9586 to Deploy Reverse Shells Without Credentials
A critical vulnerability in Sangoma Switchvox allows unauthenticated remote code execution through SQL injection in the /pa HTTP endpoint. The flaw, tracked as CVE-2026-9586 with a CVSS score of 9.3, affects internet-exposed VoIP deployments common in SMB environments. Attackers have already leveraged the issue in active campaigns since August 30, 2026, to open reverse shells and perform reconnaissance using Base64-encoded commands. The root cause is improper handling of the PhoneIP parameter in PostgreSQL queries, classified as CWE-89, which grants superuser database privileges. Sangoma released the fix in Switchvox 8.4.0.2 on July 14, 2026, following initial disclosure in April. Administrators are urged to patch immediately, restrict access, and monitor for indicators such as connections to 176.65.148.184 and suspicious entries in /var/log/switchvox/db-quirks.log.
NVD Disruptions Force Security Teams to Diversify Vulnerability Intelligence Sources
The vulnerability management ecosystem has undergone major shifts over the past two years, undermining reliance on a single authoritative database. NVD, long considered the central enrichment layer for CVE records, has experienced significant operational problems that affect timeliness and completeness of data. Russian organizations are increasingly turning to BDU FSTEC as the national vulnerability database that provides official descriptions, remediation guidance, and coverage of domestic software. CVE maintained by MITRE continues to serve as the universal identifier standard, yet it lacks the detailed scoring and product mappings previously supplied by NVD. Vendor security bulletins from Microsoft, Cisco, Astra Group, and Positive Technologies often deliver the earliest and most accurate information. The article explains why a multi-source approach has become essential for comprehensive vulnerability management programs.