Posts

🟠 High | Source: Microsoft Security Response Center CVE-2026-47729 is a memory disclosure vulnerability in Squid’s FTP gateway component, meaning an attacker could potentially extract sensitive data from memory during FTP proxying operations. This affects Azure environments where Squid is used as a proxy. Memory disclosure flaws can expose credentials, session tokens, or other sensitive data that should not be accessible to an attacker. Security Architect’s Take: Audit any Azure workloads running Squid as an FTP proxy and apply vendor patches immediately; if Squid is not explicitly required for FTP gateway functionality, consider disabling that feature or replacing Squid with a patched alternative to reduce attack surface. ...

🟠 High | Source: Microsoft Security Response Center A nil-pointer dereference vulnerability in CoreDNS’s rewrite plugin can cause a remote denial-of-service (DoS) condition. When a downstream plugin returns a DNS response lacking an OPT record, the EDNS0 response-revert logic panics, crashing the CoreDNS process. This is exploitable remotely, making it a meaningful availability risk for any Kubernetes or Azure workload relying on CoreDNS for DNS resolution. Security Architect’s Take: Identify all environments using CoreDNS with the rewrite plugin enabled — particularly AKS clusters and self-managed Kubernetes on Azure — and apply the patched CoreDNS version as soon as it is available. As an interim measure, consider restricting external DNS query paths and monitoring for unexpected CoreDNS process restarts. ...

🟠 High | Source: Microsoft Security Response Center A vulnerability in CoreDNS’s proxyproto plugin causes it to panic and crash when it receives a specifically crafted 28-byte Proxy Protocol version 2 (PPv2) datagram over a non-UDP transport. An unauthenticated remote attacker can exploit this with a single malicious packet, making it trivially easy to take down DNS resolution in affected environments. Any Kubernetes or Azure service relying on CoreDNS for internal DNS is at risk of a denial-of-service outage. ...

🟠 High | Source: Microsoft Security Response Center A use-after-free vulnerability (CVE-2026-15905) has been identified in the Aura windowing framework within the Chromium engine. Because Microsoft Edge is built on Chromium, it inherits this flaw, which could allow an attacker to execute arbitrary code or cause a crash by manipulating freed memory. Google has issued a fix via Chrome Releases, and Microsoft Edge will incorporate the patch through its standard Chromium ingestion process. ...

🟠 High | Source: Microsoft Security Response Center A use-after-free vulnerability (CVE-2026-15904) has been identified in the Ozone graphics platform layer within Chromium. Microsoft Edge, being Chromium-based, is affected and has ingested the upstream fix from Google Chrome. Use-after-free flaws can allow attackers to execute arbitrary code by manipulating freed memory, potentially compromising the browser and the underlying system. Security Architect’s Take: Ensure Microsoft Edge is updated to the latest stable release across all managed endpoints and virtual desktop environments, including Azure Virtual Desktop deployments. Validate that your endpoint management policy (e.g. Intune) is enforcing automatic browser updates and consider temporarily restricting untrusted web content access until patching is confirmed complete. ...

🟠 High | Source: Microsoft Security Response Center A memory safety vulnerability (out-of-bounds read and write) has been identified in V8, the JavaScript engine used by Chromium-based browsers including Microsoft Edge. This type of flaw can potentially be exploited by attackers to execute arbitrary code or leak sensitive data simply by directing a user to a malicious webpage. Microsoft Edge will receive a fix via its regular Chromium ingestion process. Security Architect’s Take: Ensure Microsoft Edge and any Chromium-based browsers deployed across your organisation are updated to the latest version immediately. If your environment uses browser-based access to Azure portals or internal tooling, prioritise patching on privileged workstations and Privileged Access Workstations (PAWs) first, as exploitation could compromise credentials or session tokens. ...

🟠 High | Source: Microsoft Security Response Center A use-after-free vulnerability (CVE-2026-15902) has been identified in the Cast component of Chromium, the open-source browser engine underpinning Microsoft Edge. Use-after-free flaws occur when a programme continues to reference memory after it has been freed, potentially allowing an attacker to execute arbitrary code. Microsoft Edge receives this fix via its Chromium ingestion pipeline, meaning users of Edge-based browser sessions — including those accessing Azure and Microsoft 365 services — should update promptly. ...

🟠 High | Source: Microsoft Security Response Center A use-after-free vulnerability (CVE-2026-15901) has been identified in the Network component of Chromium, the open-source browser engine that underpins Microsoft Edge. Use-after-free flaws occur when a programme continues to use memory after it has been freed, potentially allowing an attacker to execute arbitrary code. Microsoft Edge inherits this vulnerability through its Chromium dependency and is addressed via the upstream Google Chrome fix. Security Architect’s Take: Ensure Microsoft Edge is updated to the latest version across all managed endpoints and virtual machines, including Azure Virtual Desktop environments. If your organisation uses browser-based access to cloud consoles or internal tooling, prioritise this patch given the remote code execution potential of use-after-free vulnerabilities in network-handling code. ...

🟠 High | Source: Microsoft Security Response Center A use-after-free vulnerability in the GPU component of Chromium (CVE-2026-15900) has been identified and patched by Google. Microsoft Edge, which is built on Chromium, inherits this fix. Use-after-free flaws can allow attackers to execute arbitrary code by manipulating freed memory, potentially compromising the affected browser and the underlying system. Security Architect’s Take: Ensure Microsoft Edge is updated to the latest stable release across all managed endpoints and virtual desktop environments, including Azure Virtual Desktop deployments. Prioritise this in environments where users access sensitive cloud management portals via Edge. ...

🟠 High | Source: Microsoft Security Response Center A use-after-free vulnerability (CVE-2026-15899) has been identified in the CameraCapture component of Chromium, the open-source browser engine underpinning Microsoft Edge. Use-after-free flaws occur when a programme continues to reference memory after it has been freed, potentially allowing an attacker to execute arbitrary code. Microsoft Edge inherits this vulnerability from Chromium and is addressed via Google’s upstream patch. Security Architect’s Take: Ensure Microsoft Edge is updated to the latest version across all managed endpoints and virtual machines, including Azure Virtual Desktop environments. Prioritise patching for any user-facing workloads where Edge is deployed, and consider enforcing browser version compliance via Intune or Group Policy to reduce exposure windows. ...