Microsoft patches actively exploited zero-day Outlook NTLM hash theft vulnerability

Why it matters.Edge email gateways inspect inbound traffic at corporate perimeters. When chained flaws yield root execution, attackers decrypt traffic and establish persistent footholds. Infrastructure teams must apply firmware updates immediately and restrict management access from public routing.

• Vulnerability mechanics: Tracked as CVE-2026-116606 and CVE-2026-111560, the flaws affect appliance backup restoration and timezone configuration parsing.
• Exploit chain: Remote attackers exploit the alternate path authorization bypass on administrative interfaces to restore crafted backups without credentials.
• Root execution: Intruders subsequently pass shell metacharacters into timezone fields to execute arbitrary commands with root privileges.
• Appliance impact: While authorization bypass affects email gateways, the command injection flaw spans Barracuda load balancers, firewalls, and archivers.
• Remediation releases: Barracuda released firmware update 9.4.0.030 alongside hotfixes BNSF-40425 and BNSF-40430, advising teams to restrict management access.

Why it matters.Engineering teams clone external repositories daily during normal development and automated builds. When recursive submodule checkout triggers arbitrary code execution, attackers compromise developer workstations and build runners. Engineering teams must upgrade local Git tools and continuous integration container images immediately.

• Vulnerability mechanics: Tracked as CVE-2026-111760, an integer truncation bug in index path handling lets deeply nested paths bypass sanitization checks.
• Submodule exploitation: Attackers substitute a submodule git directory file with a symbolic link pointing to a malicious directory containing hook scripts.
• Execution vector: When developers recursively clone an untrusted repository, Git follows the link and executes arbitrary commands during checkout.
• Protocol vulnerabilities: The release also fixes CVE-2026-113408, a path traversal defect triggered through advertised symbolic references over Git protocol v2.
• Remediation releases: Patches shipped in Git 2.56.1 and backported across maintenance branches 2.55.1, 2.54.1, 2.53.1, 2.52.1, 2.51.3, and 2.50.2.

Why it matters.Model Context Protocol servers give artificial intelligence assistants programmatic access to cloud APIs. When case normalization errors let API calls bypass deny lists, autonomous agents execute destructive actions without required approvals. Cloud engineers must upgrade AWS API MCP servers to version 1.5.1 immediately.

• Vulnerability mechanics: Tracked as CVE-2026-125271 and GHSA-4wq9-grf3-qg2p, the defect affects security policy enforcement in awslabs.aws-api-mcp-server versions 0.2.13 through 1.5.0.
• Normalization failure: The server normalizes operation names incorrectly when evaluating API calls containing consecutive capital letters against configured policies.
• Policy evasion: Affected operations fail to match operator denyList rules, allowing artificial intelligence assistants to execute prohibited API actions without approval.
• Remediation release: AWS resolved the issue in version 1.5.1 by correcting operation name casing conversion before policy evaluation.
• Operational guidance: AWS confirmed no workaround exists, advising all teams running containerized or local MCP servers to upgrade immediately.

Why it matters.Cisco BroadWorks provides session control backbones for telecommunications carriers and large enterprise phone networks. When unauthenticated XML payloads force servers to leak configuration files, threat actors intercept carrier communications. Telecommunications engineers must apply Cisco BroadWorks maintenance patches immediately and restrict management port access.

• Vulnerability mechanics: Tracked as CVE-2026-20320, the defect resides in the Open Client Interface XML parser of Cisco BroadWorks application delivery platforms.
• Exploit method: Unauthenticated remote attackers send crafted XML messages to network ports, forcing the server to read files and open outbound channels.
• Data exfiltration: Threat actors leverage out-of-band responses to extract sensitive configuration data, cryptographic tokens, and subscriber records.
• Exploitation confirmation: CISA confirmed active in-the-wild exploitation against telecommunications providers, setting a federal remediation deadline under BOD 26-04.
• Remediation releases: Cisco released software maintenance fixes across BroadWorks Release 23.0 and Release 24.0, noting access control lists can limit port exposure.

Why it matters.Confluence Data Center hosts proprietary design documents and internal engineering wikis for enterprise teams. When unauthenticated SOAP requests trigger class deserialization and remote code execution, attackers compromise application servers. Infrastructure engineers should upgrade Confluence Data Center instances immediately and disable legacy XML-RPC endpoints.

• Vulnerability mechanics: Tracked as CVE-2026-90436, the defect stems from unsafe deserialization in the Apache Axis library inside Confluence SOAP and XML-RPC interfaces.
• Attack vector: Remote unauthenticated attackers send crafted SOAP fault requests to the Remote API endpoint, instantiating arbitrary Java classes before authentication checks.
• Configuration dependency: Systems remain vulnerable when administrators enable the Remote API setting, which legacy integrations frequently activate for scripting.
• Remediation releases: Atlassian delivered fixes in Confluence Data Center versions 9.2.28, 10.2.21, and subsequent maintenance releases.
• Workaround guidance: Administrators unable to upgrade immediately can mitigate exposure by disabling the Remote API setting through the general configuration console.

Why it matters.Enterprise messaging platforms rely on media transcoders to convert attachments into browser-safe formats for webmail users. When direct API submissions bypass administrative file filters, attackers force transcoders to process forbidden formats and expose sensitive message metadata. Messaging engineers must deploy Openwave version 1.1.22.0 immediately and isolate transcoder ports.

• Vulnerability mechanics: Tracked as CVE-2026-111793 with a 4.3 CVSS score, the defect represents an incorrect resource transfer flaw during file conversion operations.
• Restriction bypass: Attackers bypass webmail interface filters and upload crafted document structures directly to the media transcoder service component.
• Information disclosure: The transcoder processes disallowed document types, exposing internal server memory buffers and message metadata during conversion cycles.
• Exploitation status: International coordination authorities reported active in-the-wild exploitation campaigns targeting enterprise webmail environments.
• Remediation releases: Openwave Messaging released software updates in version 1.1.22.0, while CISA established a federal remediation deadline under BOD 26-04.

Why it matters.Self-managed GitLab instances serve as central source code repositories and deployment automation platforms. When repository service engines inherit Git execution flaws, malicious repository imports compromise host infrastructure and expose proprietary source code. DevOps teams must upgrade self-managed GitLab instances to versions 19.5.4, 19.4.6, or 19.3.8 immediately.

• Remediation versions: Updates shipped in versions 19.5.4, 19.4.6, and 19.3.8 for both self-managed Community Edition and Enterprise Edition deployments.
• Gitaly integration: The updates patch the underlying Gitaly service engine, incorporating upstream Git fixes for recursive clone integer truncation defect CVE-2026-111760.
• Execution hardening: The release resolves CVE-2026-105437, an issue where malformed repository configurations could trigger unexpected process execution paths during repository synchronization.
• Continuous integration updates: The builds deliver bundled security hardening for continuous integration runner execution environments and external repository mirroring tasks.
• Upgrade priority: GitLab designated the releases as strongly recommended for all self-managed instances to prevent remote attackers from abusing repository import routines.