Last updated: October 5, 2026 at 10:28 AM UTC
All 897 Vulnerability 362 Breach 144 Threat 384 Defense 7

Unpatched Cursor flaw runs a repo's fake git.exe the moment you open it

Security firm Mindgard disclosed an unpatched flaw in Cursor, the widely used AI code editor, that runs code automatically when a developer opens a malicious repository on Windows. When loading a project, Cursor looks for a Git binary in several places, including the workspace itself, so a file named git.exe planted in the repository root gets executed with no click, prompt, or warning, and it re-runs on a cadence while the project stays open. In a proof of concept, a renamed Windows Calculator launched on its own. Mindgard reported it in December and went public after seven months with no fix, so there is no patch and no CVE, only workarounds.

Check
Determine who uses Cursor on Windows, and avoid opening untrusted or freshly cloned repositories directly on a host, since a planted git.exe in the repository root runs automatically with the developer's access.
Affected
Developers using Cursor on Windows; opening a repository with a malicious git.exe in its root runs that binary automatically as the user, exposing source, SSH keys, and cloud tokens, with no patch.
Fix
Until Cursor fixes this, open untrusted repositories only in a disposable virtual machine or Windows Sandbox, add AppLocker path-deny rules for executables under workspace folders, and watch for unexpected child processes.

Researcher drops unpatched Windows privilege-escalation zero-day right after Patch Tuesday

Less than an hour after Microsoft's July Patch Tuesday, the researcher known as Nightmare Eclipse published a proof-of-concept for LegacyHive, a Windows privilege-escalation flaw that works on fully updated systems. It abuses the Windows User Profile Service to let a standard user load another user's registry hive, including an administrator's, into their own profile, a useful stepping stone for an attacker who already has a foothold. There is no CVE, advisory, or patch. The public proof-of-concept was deliberately stripped down, needing extra credentials, but the researcher says the original had no such limits. Given this researcher's flaws have been weaponized quickly before, defenders should not wait for a fix.

Check
Since there is no patch, limit who can create local standard-user accounts, and monitor the Windows User Profile Service for unexpected registry hive loads and access to NTUSER.DAT and UsrClass.dat files.
Affected
Fully patched Windows desktops and servers; an attacker with a standard-user foothold and credentials can use LegacyHive to load another user's registry hive and help escalate privileges, with no fix yet.
Fix
Apply Microsoft's fix as soon as it ships, and until then restrict local account creation, watch for suspicious profile-service and registry activity, and validate the proof-of-concept only in isolated test environments.

Attacker ran an entire botnet through Google's Gemini CLI using plain-language prompts

Trend Micro documented a Russian-speaking attacker who used Google's open-source Gemini CLI as a hands-on hacking assistant to build and run a small botnet. Across more than 200 sessions, a jailbroken Gemini took the role of an "authorized pen tester," saved stolen credentials, and even suggested improvements dozens of times. Working from a roughly 5KB set of plain-text files holding a jailbreak prompt and a command-and-control playbook, the AI handled the operation through natural-language requests: at one point it migrated the entire command server to a new host with a Cloudflare tunnel in about six minutes and debugged its own errors. The malware itself was crude; the AI was the force multiplier.

Check
Consider how AI command-line tools and agents are used and monitored in your environment, and watch for jailbroken AI assistants and the credential theft and command-and-control activity they can drive.
Affected
Any organization where attackers can run AI coding assistants against its systems; a jailbroken AI CLI let a low-skill operator build, run, and repair botnet infrastructure through plain-language prompts.
Fix
Restrict and monitor AI agent and CLI usage, enforce guardrails that resist jailbreaking, apply least privilege and network controls so a compromised agent's reach is limited, and hunt for unusual command-and-control traffic.

AsyncAPI npm packages backdoored through a hijacked build pipeline

Attackers backdoored several widely used @asyncapi npm packages, together drawing around three million weekly downloads, by hijacking the project's GitHub Actions build pipeline rather than stealing a maintainer's npm token. Because the project's own release workflow published the malicious versions, they carried valid provenance signatures, which prove where a package came from but not that the code was trustworthy. The payload was hidden in normal runtime files behind trailing whitespace and ran when the module was imported, not on install, so defenses aimed at install scripts missed it. Once loaded, it fetched an encrypted second stage, stole credentials and cloud and registry tokens, and planted persistence, even in developer tool configuration files.

Check
Check whether your projects or CI pulled the affected @asyncapi versions, focusing on systems that imported the modules, not only installed them, and review developer and build environments for stolen tokens.
Affected
Developers and CI pipelines that imported the compromised @asyncapi versions; the malware steals credentials, cloud keys, and npm and GitHub tokens and adds persistence, and valid provenance signatures made them look trustworthy.
Fix
Downgrade to the clean @asyncapi versions, remove the bad ones from lockfiles, caches, and mirrors, rotate credentials reachable from affected machines from a clean system, and harden CI against untrusted pull-request triggers.

OkoBot malware injects fake seed-phrase prompts into real Ledger and Trezor apps

Kaspersky detailed OkoBot, a Windows malware framework active since 2025 whose standout module, SeedHunter, tricks hardware-wallet owners into giving up their recovery phrase. On an infected PC, the malware waits for wallet software like Ledger Live, Ledger Wallet, or Trezor Suite, sometimes until the device is plugged in, then displays a malicious page asking for the seed phrase from inside the wallet's own genuine app. Because the surrounding application is the real one the victim installed, the request looks legitimate, but anyone who types in the phrase hands over full control of their funds. Kaspersky counted hundreds of victims across more than 25 countries, and the framework remains active.

Check
Remind cryptocurrency users that hardware wallets never ask for the recovery phrase to be typed into a computer, and any prompt requesting it, even inside the real wallet app, is a scam.
Affected
Hardware-wallet owners on OkoBot-infected Windows PCs; the malware injects a fake recovery-phrase request into the genuine Ledger or Trezor desktop app, and victims who enter the phrase lose control of their cryptocurrency.
Fix
Never enter a wallet recovery phrase into any computer prompt, keep endpoints protected to catch OkoBot, and confirm sensitive actions on the hardware device's own screen rather than the desktop app.

Microsoft's record Patch Tuesday fixes 622 flaws, including two exploited zero-days

Microsoft shipped its largest Patch Tuesday on record, fixing 622 vulnerabilities, more than triple June's previous high, and two of them are already being exploited. Both live bugs are privilege-escalation flaws in identity and collaboration infrastructure rather than flashy remote code execution: CVE-2026-56164 in on-premises SharePoint Server lets an unauthenticated attacker escalate over the network, and CVE-2026-56155 in Active Directory Federation Services lets an authenticated attacker gain higher privileges, both found by incident responders inside real attacks. A third zero-day, a BitLocker bypass needing physical access, was publicly disclosed but not exploited. The sheer volume, driven partly by AI-assisted bug finding, makes prioritizing by exploitation status, not severity score, essential this month.

Check
Prioritize the two actively exploited flaws first: patch on-premises SharePoint Server and AD FS immediately, then internet-facing and identity systems, and confirm updates actually installed given the volume.
Affected
Organizations running on-premises SharePoint Server or AD FS are at immediate risk from the exploited zero-days (CVE-2026-56164, CVE-2026-56155); the wider release also affects Windows, Office, Exchange, SQL Server, and more.
Fix
Deploy the July updates, leading with the exploited SharePoint and AD FS flaws, review authentication and privilege-change logs on those systems, and enable AMSI in Full Mode on SharePoint.

SonicWall SMA1000 remote-access appliances hit by exploited zero-day flaws

SonicWall is warning that two flaws in its SMA1000 remote-access appliances are being actively exploited as zero-days, and has released hotfixes. CVE-2026-15409 is an unauthenticated server-side request forgery bug in the appliance's WorkPlace interface that lets an attacker make the device send requests to internal systems, turning an edge gateway into a pivot point. CVE-2026-15410 is a code-injection flaw in the management console that lets an administrator run operating-system commands, and SonicWall rates the overall advisory a top CVSS score of 10.0. Both were added to CISA's exploited-vulnerabilities catalog, with a federal deadline of July 17. Because exploitation is confirmed, any unpatched appliance should be treated as potentially compromised.

Check
Identify all SonicWall SMA1000 appliances, including standby and disaster-recovery nodes, apply the hotfix immediately, and review authentication logs, new accounts, outbound connections, and configuration changes for signs of intrusion.
Affected
Organizations running SonicWall SMA1000 remote-access appliances (CVE-2026-15409, CVE-2026-15410); attackers are actively exploiting the flaws, and the request-forgery and code-injection bugs could be chained to reach and run commands on internal systems.
Fix
Apply SonicWall's hotfix now, restrict management interfaces to trusted networks until patched, and because exploitation is confirmed, run a compromise assessment and assume unpatched appliances may already be backdoored.

Old Microsoft-signed Linux boot files let attackers bypass Secure Boot on most PCs

Researchers at ESET found 11 old Microsoft-signed Linux boot components, called shims, that can be used to bypass UEFI Secure Boot on almost any PC, regardless of its operating system. The trick needs no new vulnerability: because these shims were signed years ago with a trusted Microsoft certificate and never revoked, an attacker with admin or boot-level access can copy an old vulnerable shim onto a machine and run untrusted code before the operating system loads. That enables stealthy bootkits that survive reinstalls and start before security tools. Microsoft revoked all 11 in June by blocklisting their hashes, which Windows applies automatically and Linux systems can pull through firmware updates.

Check
Confirm the June UEFI revocation update reached your systems: Windows applies it automatically, while Linux hosts should pull it through the firmware update service, and use ESET's check for the revoked hashes.
Affected
Almost any UEFI-based computer trusting Microsoft's third-party 2011 certificate (CVE-2026-8863, CVE-2026-10797), regardless of operating system; an attacker with boot-level access can load an old signed shim to defeat Secure Boot.
Fix
Apply the UEFI revocation update on Windows and Linux, disable third-party UEFI signing where it is not needed, consider Secured-core hardware, and protect against the admin access these attacks require.

RabbitMQ flaws leak the broker's OAuth secret and expose cross-tenant data

Researchers at Miggo disclosed two access-control flaws in RabbitMQ, the widely used message broker, that have been present since early 2024. In the more serious one, an obsolete management endpoint had its authorization check hard-coded to always allow, so an unauthenticated attacker can leak the broker's confidential OAuth client secret in a single request, a direct path to full broker takeover where that secret is used. The second lets any logged-in user, even one with no assigned permissions, read other tenants' queue and exchange metadata, useful reconnaissance in shared environments. Both are fixed in updated releases, and the risk is sharpest where the management port is reachable from untrusted networks.

Check
Identify RabbitMQ instances on affected 3.13 and later releases, check whether the management interface and port 15672 are reachable from untrusted networks, and confirm how the OAuth client secret is configured.
Affected
RabbitMQ deployments from release 3.13.0 onward (CVE-2026-57219, CVE-2026-57221), especially cloud or multi-tenant setups with the management port exposed; attackers can leak the OAuth secret or read other tenants' metadata.
Fix
Update to a fixed RabbitMQ release, rotate the OAuth client secret if the management interface was internet-reachable, restrict access to port 15672, separate tenants by virtual host, and firewall the vulnerable endpoint.

148 npm packages posed as student proxies to turn browsers into a DDoS botnet

Researchers at JFrog found 148 npm packages that abused the registry not to attack developers but as free hosting for a booby-trapped web proxy aimed at students trying to bypass school filters. Anyone who opened one of the proxy sites had their browser quietly conscripted into a distributed denial-of-service botnet, flooding target servers with HTTP and WebSocket traffic, alongside injected ads and tracking. Crucially, the packages contained no install-time scripts and were never meant to be added to a project, so dependency scanners and install sandboxes, which watch what runs on install, would not catch them. The operators can re-arm the dormant attack code with a single commit.

Check
Consider that npm and similar registries can host malicious web content, not just installable code; watch for browsers reaching proxy or tutoring-themed sites backed by package registries, and block known campaign domains.
Affected
Anyone, especially students, who visits one of these registry-hosted proxy sites; their browser is silently used to launch denial-of-service attacks, while organizations may see the resulting traffic from their networks.
Fix
Block the campaign's known package and domain indicators, educate users that free web proxies can weaponize their browsers, and treat public package registries as potential malware-hosting infrastructure, not just a dependency source.