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

CISA flags exploited Ray flaw that lets a website run code on developer machines

CISA added a critical flaw in Ray, the open-source framework for scaling AI and machine-learning workloads, to its exploited-vulnerabilities catalog and gave federal agencies just three days to fix it. Tracked as CVE-2025-62593 and scored 9.4, the bug stems from Ray leaving key dashboard and job endpoints unauthenticated; its only browser defense checked that the request's user-agent began with Mozilla, which attackers can forge. Combined with a DNS rebinding attack, a malicious website or advertisement viewed while running Ray can execute code on the developer's machine. A DDoS botnet adopted it before public disclosure, and a separate campaign has been turning unpatched Ray clusters with GPUs into cryptocurrency miners.

Check
Upgrade Ray to version 2.52.0 or later, and treat the risk as immediate given the three-day federal deadline and ongoing campaigns against exposed clusters, including developer machines running Ray locally.
Affected
Anyone running Ray before 2.52.0 (CVE-2025-62593); unauthenticated dashboard endpoints plus a browser and DNS rebinding attack let a malicious page run code on the machine, and it is exploited in the wild.
Fix
Patch to 2.52.0, keep Ray dashboards and APIs off untrusted networks and behind authentication, restrict who can reach them, and check GPU clusters for unauthorized cryptomining and other signs of compromise.

Exploited MLflow SSRF flaw lets attackers steal cloud credentials from ML servers

Attackers began exploiting a critical unauthenticated flaw in MLflow, the popular open-source machine-learning platform, within hours of its disclosure. Tracked as CVE-2026-64849 and scored 9.3, the server-side request forgery bug lives in the model-registry webhook testing feature: an attacker hosts an endpoint that passes validation, then redirects MLflow to internal targets such as the cloud metadata service or loopback addresses, and MLflow returns their responses. That exposes cloud credentials, API tokens, and secrets. Because MLflow sits close to training data, artifacts, object storage, CI/CD, and inference pipelines, a compromise offers both credentials and a foothold for lateral movement. watchTowr's honeypots saw exploitation attempts almost immediately.

Check
Upgrade MLflow to version 3.15.0 or later immediately, and treat any internet-exposed instance on an earlier version as potentially probed, checking for signs of metadata access.
Affected
Organizations running MLflow before 3.15.0, especially cloud-hosted and internet-exposed (CVE-2026-64849); an unauthenticated attacker can coerce it into fetching internal targets and leak cloud credentials, tokens, and secrets.
Fix
Patch to 3.15.0, review webhook configurations for attacker URLs, inspect logs for webhook-test requests and metadata or loopback addresses, rotate credentials the server could reach, and restrict its network exposure.

Ransomware gangs now exploit a Windows Task Host flaw to gain SYSTEM

CISA confirmed that ransomware groups are now exploiting a Windows Task Host privilege-escalation flaw that has been flagged as actively exploited since April. Tracked as CVE-2025-60710 and scored 7.8, it is a link-following weakness in the component that runs background scheduled tasks as SYSTEM: a local attacker with only basic user rights can use a junction on a user-writable path to make a SYSTEM-level task act on files it should not, escalating to full control. Microsoft patched it in November 2025, and it affects Windows 11 and Server 2025. Privilege escalation like this is exactly what ransomware operators need to disable defenses and spread after gaining an initial foothold.

Check
Confirm the November 2025 update for this flaw is deployed across Windows 11 and Windows Server 2025 systems, prioritizing any that still lack it, since ransomware crews are now using it.
Affected
Windows 11 and Windows Server 2025 systems missing the November 2025 patch (CVE-2025-60710); a local attacker with basic rights can escalate to SYSTEM, and ransomware groups are actively exploiting it.
Fix
Apply the patch, prioritize privilege-escalation fixes in your patching since they enable ransomware to spread, monitor for junction abuse and unexpected SYSTEM-level file operations, and limit local footholds through least privilege.

Researchers trick Microsoft Copilot into revealing its own data-exfiltration bypass

Varonis disclosed a flaw in Microsoft Copilot Personal, the consumer assistant, that could let a single click exfiltrate data from connected apps, and the way they found it is striking. Tracked as CVE-2026-24301 and named CoSnitch, the technique had the researchers repeatedly ask Copilot why a prompt could not run without user interaction; each refusal added a technical justification, until the assistant named a hidden parameter, the exact session conditions where it worked, and the protections meant to block it. Building the request as described, the bypass ran. Varonis said Copilot was not breached but played. Related research showed attacker pages persisting unwanted memory in Copilot through indirect prompt injection.

Check
Treat AI assistants with access to connected apps and persistent memory as a data-exfiltration and manipulation surface, and review what apps and data your assistants can reach on a single user action.
Affected
Users of AI assistants like Microsoft Copilot Personal connected to email and other apps; a crafted link can drive the assistant to leak connected-app data or persist attacker instructions in its memory.
Fix
Limit which apps and data assistants can access, apply vendor updates, be cautious with links that invoke an assistant, and watch for unexpected actions, since a refusal does not close a bypass.

Self-spreading prompts can jump between AI agents through shared state files

Researchers, including teams at Anthropic and EPFL, demonstrated that self-propagating instructions can spread from one AI agent to another through the editable prompt and state files that autonomous agent harnesses use to carry context between sessions. In simulated multi-agent coding setups, a payload written into a shared file could infect the next agent that read it. The researchers call the risk real but currently limited, noting there is no sign of it spreading in the wild and that compromising one agent usually already grants machine access. Encouragingly, adding a single short warning paragraph to an agent's system prompt cut propagation to nearly zero across the payloads they tested.

Check
If you run autonomous or multi-agent setups, treat their persistent prompt and state files as an integrity boundary, and review what those files contain and which agents can write to them.
Affected
Autonomous and multi-agent systems that share editable prompt or state files between agents or sessions; a malicious instruction written into such a file can propagate to other agents that read it.
Fix
Control and review writes to shared agent state, add a system-prompt warning that cut propagation to near zero in testing, isolate agents and their files, and monitor state files for unexpected instructions.

Sixteen typosquatted RubyGems packages steal browser logins and crypto wallets

Researchers flagged a typosquatting campaign, tracked as StubMaker, that planted sixteen malicious packages on RubyGems to deliver a Windows information stealer. The packages imitate popular Ruby dependencies with clumsy misspellings, betting that a developer will mistype a name during installation. Once installed, the malware harvests browser credentials, cryptocurrency wallets and seed phrases, and Telegram data from the developer's machine. The campaign's name refers to its trick of faking a build toolchain so a malicious install looks like a routine one. It is the latest reminder that open-source package registries remain an easy delivery route for stealers aimed at developers.

Check
Double-check RubyGems dependency names before installing, watch for clumsy misspellings of popular gems, and scan developer machines and CI for the malicious packages if you use Ruby.
Affected
Ruby developers who mistype or fail to verify gem names during installation; the malicious packages install a Windows stealer that takes browser logins, cryptocurrency wallets and seed phrases, and Telegram data.
Fix
Pin and verify dependency names and sources, use lockfiles, prefer tooling that flags typosquats, rotate credentials and wallets on any machine that installed a bad gem, and keep wallets off dev machines.

Critical GitLab flaw lets unauthenticated attackers delete public projects and data

GitLab shipped an out-of-band critical patch for a flaw that lets an unauthenticated attacker remotely modify or delete public projects and user data through a GraphQL directive. Tracked as CVE-2026-19478 and scored 9.4, it affects self-managed Community and Enterprise installations; GitLab.com and Dedicated are already fixed. The company released it outside its normal twice-monthly schedule, and the fixed versions are 19.2.4, 19.1.6, 19.0.8, and 18.11.11, with the 18.2 through 18.10 branches left in the affected range and needing an upgrade. A second, lower-severity GraphQL flaw involving cross-site request forgery was fixed in the same release. GitLab reports no known exploitation yet.

Check
Upgrade self-managed GitLab to a fixed release immediately, and if you run a version between 18.2 and 18.10, plan an upgrade since those branches did not receive a backported fix.
Affected
Organizations running self-managed GitLab Community or Enterprise Edition (CVE-2026-19478); an unauthenticated attacker can remotely modify or delete public projects and user data through a GraphQL directive.
Fix
Apply the out-of-band patch now, prioritize internet-reachable instances, review logs for unexpected GraphQL activity and project or user changes, and restore any affected projects from backups if tampering is found.

Unauthenticated Forminator flaw lets attackers upload PHP and take over WordPress sites

A critical flaw in Forminator Forms, a WordPress plugin with more than 600,000 installations, lets unauthenticated attackers upload executable PHP files and take over a site. Tracked as CVE-2026-15748 and scored 9.8, the bug chains weaknesses in the plugin's upload handling: an attacker smuggles a forged record through a Select field that declares itself a file upload, then slips a PHP file past a blocklist that only checks exact extensions. Exploitation requires a form with both a file upload field and a select field, and it affects all versions up to 1.56.1. Because it needs no authentication, automated scanners can hunt for vulnerable sites at scale.

Check
Update the Forminator plugin to a version newer than 1.56.1 across all WordPress sites, and check for unexpected PHP files in upload directories and unfamiliar administrator activity.
Affected
WordPress sites running Forminator 1.56.1 or earlier with a form containing both a file upload and a select field (CVE-2026-15748); an unauthenticated attacker can upload PHP and fully compromise the site.
Fix
Patch the plugin, put a web application firewall in front of the site, scan for web shells and unauthorized files, and remove or reconfigure vulnerable forms until the update is applied.

Unisoc modem exploit chain reaches the Android kernel through a video call

Researchers at SSD Secure Disclosure published a two-stage exploit chain that gains full Android kernel access on devices using Unisoc modem firmware, triggered by a VoLTE video call. The first stage, disclosed earlier this year, is remote code execution in the modem via a malformed call; the new second stage abuses a memory-isolation weakness in the modem to disable its protections and reach kernel memory. Pulling it off requires the attacker to run a rogue 4G network and the victim to answer the call. The affected firmware is shared across several Unisoc chipsets used in budget phones from brands like Motorola, Realme, and Xiaomi, and there is no fix from the chipmaker.

Check
Identify devices using affected Unisoc chipsets in your fleet, and since there is no vendor patch, watch for manufacturer firmware updates and weigh the risk for devices on untrusted cellular networks.
Affected
Android devices built on affected Unisoc chipsets, common in budget phones and some embedded and vehicle systems; an attacker on a rogue network can chain a video call into kernel access.
Fix
Press device makers for firmware updates, treat the modem as an untrusted boundary in device designs, and restrict exposure to rogue cellular networks where possible, since the attack needs an answered call.

GitHub issue title let an AI agent hijack Snowflake CI and steal a token

Researchers at Wiz found that a public Snowflake code repository could be hijacked through nothing more than a crafted GitHub issue title. A workflow that ran when issues were opened dropped the attacker-controlled title straight into a command, so an unauthenticated user could run code on the GitHub Actions runner and steal a Jira API token used by the automation. The notable twist is how the bug arrived: it was introduced days earlier by an AI tool meant to fix security issues, and an AI code reviewer approved the change. Snowflake fixed it by passing the title safely as an argument rather than expanding it into a command.

Check
Audit GitHub Actions workflows that run on untrusted input like issue titles or pull requests, and never interpolate that input directly into shell commands; pass it as environment variables or arguments.
Affected
Repositories whose workflows trigger on issues or pull requests and interpolate attacker-controlled text into commands; an unauthenticated user can run code on the runner and steal the secrets the workflow holds.
Fix
Sanitize untrusted workflow input, minimize the secrets and permissions each workflow can access, and do not assume AI-generated or AI-reviewed code is safe, since automated fixes and reviews miss injection flaws.