Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7

Attackers steal SharePoint machine keys in one request after exploit code goes public

Attackers began exploiting a critical Microsoft SharePoint flaw within days of a working proof-of-concept appearing publicly. CVE-2026-50522 is a deserialization of untrusted data issue rated 9.8 that lets a remote attacker run code on on-premises SharePoint without authentication, and Microsoft patched it in the July updates while marking exploitation as more likely rather than confirmed. Offensive security firm watchTowr reports active attacks against on-premises deployments, with attackers pulling SharePoint machine keys in a single request. Those keys let an attacker forge authentication tokens and impersonate users, so access survives patching. It is the third SharePoint flaw to see exploitation this month.

Check
Apply July's SharePoint updates, then rotate machine keys on any on-premises server that was internet-reachable, since patching alone does not evict an attacker who already pulled them.
Affected
Organizations running on-premises SharePoint Server 2016, 2019, or Subscription Edition (CVE-2026-50522); unauthenticated attackers run code and steal machine keys that let them forge tokens and keep access after patching.
Fix
Patch, rotate machine keys and any credentials the server handled, hunt for web shells and forged token use, and restrict internet exposure of on-premises SharePoint deployments.

Qilin ransomware crews break in through a Palo Alto VPN authentication bypass

Arctic Wolf Labs investigated multiple intrusions in June that began by exploiting an authentication bypass in Palo Alto Networks PAN-OS and ended in Qilin ransomware. CVE-2026-0257 affects the portal and gateway components and lets an unauthenticated remote attacker establish a VPN session without valid credentials, but only where authentication override cookies are enabled alongside specific certificate configurations. That narrow precondition makes it easy to assume you are unaffected without checking. The flaw is patched. Because it grants VPN access rather than code execution, the intrusions look like ordinary remote logins at the start, which delays detection until ransomware is deployed.

Check
Confirm PAN-OS is patched against this flaw and check whether authentication override cookies are enabled with the certificate configurations that make it exploitable, since the precondition is easy to overlook.
Affected
Organizations running unpatched PAN-OS portal or gateway components with authentication override cookies enabled (CVE-2026-0257); attackers establish VPN sessions without credentials, and Qilin affiliates have used this for initial access.
Fix
Patch PAN-OS, disable authentication override cookies where not required, require multi-factor authentication on VPN access, and hunt for VPN sessions lacking a corresponding authentication event or coming from unexpected locations.

Hidden pull request comments can hijack AI agents via Microsoft's DevOps MCP server

Offensive security firm Manifold Security detailed a confused deputy flaw in Microsoft's official Azure DevOps MCP server, which lets AI agents read and operate Azure DevOps on a user's behalf across pull requests, pipelines, wikis, and work items, using that user's own permissions. One of the server's tools returns pull request descriptions without the prompt injection guardrail Microsoft had already applied to other tools. Because descriptions accept Markdown, an attacker can bury instructions in an HTML comment: the web interface renders it as nothing, so a reviewer sees an ordinary change, while the REST API returns the text verbatim and hands it straight to the agent.

Check
Check whether AI agents in your environment use the Azure DevOps MCP server, and review what permissions those agents inherit, since content written by others becomes instructions the agent may act on.
Affected
Teams running AI agents against Azure DevOps through Microsoft's MCP server; a pull request description containing a hidden HTML comment can steer the agent, which acts with the requesting user's full permissions.
Fix
Treat repository and ticket content reaching an agent as untrusted input, scope MCP server permissions well below the user's own, require human approval for write actions, and monitor agent tool calls.

Poisoned web page could rewrite AWS Kiro's config file and run code

Researchers at Intezer showed that a poisoned web page could take over AWS Kiro, an AI coding tool, by getting the agent to rewrite the file that governs what it is allowed to run. A prompt injection in fetched content drops custom code into the MCP settings file, which executes the moment the file is saved. The same write to execution path was demonstrated on Kiro's release day in July 2025 by another researcher, who also flagged writing to a Visual Studio Code settings file to allowlist shell commands. AWS added an approval prompt, but only in supervised mode, leaving the default autonomous mode writing the file unprompted.

Check
If you use AWS Kiro or similar agentic coding tools, check which mode they run by default and whether the agent can write its own MCP or editor configuration files without approval.
Affected
Developers running AWS Kiro in its default autonomous mode; content fetched from a web page can inject instructions that rewrite the agent's MCP settings file, and saving that file executes attacker-supplied code.
Fix
Require approval for agent writes to configuration files in every mode, keep those files outside what the agent can modify, and treat fetched web content as untrusted rather than trusting mode settings.

Sandbox escapes in Cursor, Codex, Gemini CLI, and Antigravity let agents run code

Researchers at Pillar Security demonstrated sandbox escapes across four widely used AI coding agents: Cursor, OpenAI Codex CLI, Google Gemini CLI, and Antigravity. In nearly every case the agent never broke the sandbox directly; it only had to write a file that a trusted component outside the sandbox would later run, load, or scan. Failure modes included hook abuse, editing a virtual environment interpreter the editor then ran itself, planting Git metadata outside a .git folder to fire execution through fsmonitor, and a command allowlist that trusted a tool by name while the real invocation was not read only. Prompt injection in workspace content was the trigger.

Check
Update Cursor to 3.0.0 or later and Codex CLI to 0.95.0 or later, then check whether coding agents can reach a Docker socket or other privileged local daemon.
Affected
Developers running AI coding agents on untrusted repositories; prompt injection in workspace content can make the agent write files that trusted tools outside the sandbox later execute, defeating the sandbox.
Fix
Patch the affected agents, treat repository content as untrusted input, keep privileged daemons and sockets out of agent reach, and do not rely on a workspace sandbox as your only boundary.

SonicWall VPN appliances were backdoored for weeks before the flaws were disclosed

Incident response firm Volexity detailed how attackers chained two SonicWall SMA1000 flaws as zero-days weeks before the vendor disclosed them, reaching root and installing malware built specifically for the appliances. A previously unknown actor it tracks as UTA0533 began exploiting on June 22, nearly three weeks before the July 14 advisory. The chain starts with CVE-2026-15409 against the /wsproxy endpoint, letting an unauthenticated attacker open WebSocket tunnels to services meant to be reachable only from the appliance itself, then uses CVE-2026-15410 for command execution. With root, the actor could read stored credentials, capture traffic, and intercept credentials the appliance processes.

Check
Patch SMA1000 appliances to the fixed releases, then check them against Volexity's published indicators, since patching alone does not remove an implant left during the pre-disclosure exploitation window.
Affected
Organizations running SonicWall SMA1000 6210, 7210, or 8200v appliances (CVE-2026-15409, CVE-2026-15410); attackers held root before patches existed, with malware purpose-built for these devices and access to processed credentials.
Fix
Where indicators are found, SonicWall advises re-imaging hardware or redeploying virtual appliances, changing all user and administrator passwords, and resetting one-time-password tokens, since credentials the appliance handled should be treated as exposed.

Public exploits released for WordPress core flaws that give anonymous code execution

Public exploit code is now available for wp2shell, a pair of WordPress core flaws that chain into pre-authentication remote code execution against a stock site with no plugins installed. CVE-2026-63030 is a route confusion bug in the REST API batch endpoint, which has shipped enabled by default since 2020, and CVE-2026-60137 is a SQL injection in the author parameter handling of WP_Query. Chained, an anonymous HTTP request can run code on the server. The chain affects WordPress 6.9.0 through 6.9.4 and 7.0.0 through 7.0.1, fixed in 6.9.5 and 7.0.2, and WordPress enabled forced automatic updates given the severity.

Check
Confirm every WordPress site you run, including forgotten and staging instances, is on 6.9.5 or 7.0.2 or later, then check logs and web directories for web shells.
Affected
Any site on WordPress 6.9.0 to 6.9.4 or 7.0.0 to 7.0.1 (CVE-2026-63030, CVE-2026-60137); no plugins, login, or user interaction are needed, and working exploits are public.
Fix
Update to WordPress 6.9.5 or 7.0.2, confirm auto-updates applied, put a web application firewall in front of exposed sites, and treat unpatched internet-facing installs as potentially compromised.

Critical nginx flaw lets unauthenticated requests crash workers and may allow code execution

F5 patched a critical nginx vulnerability that lets a remote, unauthenticated attacker trigger a heap buffer overflow in the worker process with crafted HTTP requests. CVE-2026-42533 sits in nginx's script engine, the code that builds strings from configuration directives at request time, and only surfaces under a specific configuration: a regex based map whose output is referenced in a string expression after an earlier regex capture. Under that pattern the engine's two pass evaluation disagrees on buffer size. Triggering it crashes or restarts the worker, and F5 says code execution may be possible where address randomization is disabled or bypassed. Fixes shipped July 15.

Check
Check your nginx version and upgrade to 1.30.4, 1.31.3, or NGINX Plus 37.0.3.1 or later, and audit configurations for a regex map referenced after an earlier capture.
Affected
Organizations running nginx or NGINX Plus builds earlier than the July 15 fixes (CVE-2026-42533) with the vulnerable directive pattern; unauthenticated requests can crash workers and may allow code execution.
Fix
Upgrade to the fixed nginx releases, since patches for earlier nginx flaws do not cover this one, keep address space randomization enabled, and review configurations for the vulnerable map pattern.

Critical ServiceNow AI Platform flaw now exploited in attacks

A critical flaw in the ServiceNow AI Platform is now being exploited in attacks. ServiceNow disclosed CVE-2026-6875 on July 13 in advisory KB3137947, describing it as a sandbox escape that lets an attacker bypass intended platform restrictions and execute code, and noting that exploitation does not require authentication. The AI Platform underpins much of the company's IT service management and workflow tooling, and the flaw affects both hosted and self-hosted deployments. ServiceNow deployed fixes to its hosted instances and released updates for self-hosted customers. Because these instances commonly connect to identity systems, cloud services, and endpoint management tools, a compromised one is a strong pivot point.

Check
Confirm your ServiceNow family release includes the fix for this flaw, prioritize self-hosted and internet-reachable instances, and review platform and AI feature logs for anomalous activity.
Affected
Organizations running unpatched ServiceNow AI Platform deployments (CVE-2026-6875), hosted or self-hosted; unauthenticated attackers can escape the sandbox and run code on a platform wired into identity, cloud, and endpoint systems.
Fix
Apply the fixed release for your family, verify hosted instances received the update, restrict instance exposure, and rotate integration tokens if compromise is suspected, while monitoring for unusual record changes.

7-Zip fixes code execution flaw triggered by opening a crafted archive

7-Zip has released version 26.02 to fix a remote code execution vulnerability that can be triggered when a user opens a specially crafted compressed file. The archiving tool is installed on a very large number of Windows systems and is routinely used to open attachments and downloads, so a flaw that fires on opening an archive is attractive to attackers who rely on phishing. There are no reports of active exploitation so far. Similar archiving tool flaws have been weaponized quickly in the past: a WinRAR vulnerability was used last year by a Russian group in phishing attacks to install malware, so patching early matters.

Check
Update 7-Zip to version 26.02 across workstations and servers, including copies bundled inside other software or installed manually outside your patch management system.
Affected
Anyone running 7-Zip before version 26.02; opening a malicious archive received by email or download can lead to code execution, a pattern attackers have abused in past archiving tool flaws.
Fix
Install 7-Zip 26.02, inventory manually installed copies that patch tooling may miss, and remind users to treat unexpected archive attachments with caution since opening one can be enough.