Three Windows Defender privilege escalation zero-days — BlueHammer (CVE-2026-33825), RedSun, and UnDefend — are actively exploited in the wild. Microsoft patched BlueHammer in April 2026; RedSun and UnDefend remain unpatched. All three enable SYSTEM-level access from a low-privileged account.
A critical, unauthenticated remote code execution vulnerability (CVE-2026-0300, CVSS 9.3) in Palo Alto Networks PAN-OS firewalls is being actively exploited by a state-sponsored threat group. Patches are not yet available. Here is what SMBs need to do right now to protect their networks.
CVE-2026-32202 lets attackers steal Windows credentials with zero clicks. CISA deadline was May 12, 2026. Learn what SMBs must do immediately.
A critical authentication bypass (CVE-2026-41940, CVSS 9.8) in cPanel & WHM is being mass-exploited to deploy “Sorry” ransomware, compromising over 44,000 servers worldwide. Small businesses running web servers or shared Linux hosting face complete data loss. Patches are available now—immediate action is required.
Temecula-area businesses need secure, responsive IT support. Learn how Lone Wolf Networks helps reduce downtime, strengthen cybersecurity, and support growth.
This is a short post to help anyone who may have been temporarily stumped trying to enable per-VM EVC for VMotion between clusters.
If you want to know more about per-VM Enhanced VMotion Compatibility, check out the VMWare KB HERE
I was recently working on a UniFi deployment which included a UniFi cloud key gen 2 plus. The cloud key came from Ubiquiti with firmware version 0.9.8. Attempting to update the firmware resulted in the error “something went wrong” without getting past 1% on the progress.
Updating the controller and protect software was successful, but attempting to update the cloud key firmware from within the network application also failed.
When deploying VMWare VCSA in a lab environment the installer often gets stuck at stage 2 starting services. In my case, starting authentication network 2%. This seems to be an issue with VCSA wanting to verify the SSO domain through DNS resolution.
The solution for me was to create an entry in the hosts file of the VCSA appliance through SSH to the CLI. Before doing so, it is best to start from scratch. Delete the partially deployed VCSA appliance. Deploy VCSA through Stage 1 but do not enter Stage 2.
interface GigabitEthernet0/0.4
encapsulation dot1q 4
ip address 10.2.1.1 255.255.255.0
Testing with https://www.testconnectivity.microsoft.com/ shows green across the board. If you are dealing with this issue, start with this tool and run the following tests:
Testing with Microsoft Lync Connectivity Analyzer showed ready for 2013 mobility client.
After examining the Lync Front End server event log, I found event 32054, LS Storage service:
Storage Service had an EWS Autodiscovery Failure. The underlying connection was closed. Could not establish a trust relationship SSL/TLS.
The issue would seem to be the published autodiscover Uri for Exchange not matching the installed certificate on the Exchange 2016 DAG members. The Uri in the event log was reporting autodiscover.domain.local. The certificates and all other services in the infrastructure were pointing to autodiscover.domain.org. On the Exchange server, running powershell Get-ClientAccessService | fl AutoDiscoverServiceInternalUri will display the currently assigned URLs.
Issuing a Set-CsClientAccessService -Identity exchange.domain.local -AutoDiscoverServiceInternalUri https://autodiscover.domain.org/Autodiscover/Autodiscover.xml for both servers in the Exchange DAG solved the mobility client address book issue.
All rights reserved. Developed by Lone Wolf Networks, LLC
Recent Comments