Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7

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.

CISA orders agencies to patch two exploited Fortinet FortiSandbox flaws

CISA has added two critical Fortinet FortiSandbox vulnerabilities to its exploited-vulnerabilities catalog and ordered federal agencies to patch them by July 19. Tracked as CVE-2026-39808 and CVE-2026-25089, both are operating-system command injection flaws that let an unauthenticated attacker run commands remotely with low complexity and no user interaction. Fortinet disclosed and fixed them in April and June, and threat intelligence firm Defused reported in-the-wild abuse of FortiSandbox flaws in June. FortiSandbox is a threat-detection appliance, and Fortinet gear sits at many network edges, so these devices are a recurring target in espionage and ransomware campaigns, making prompt patching important.

Check
Identify Fortinet FortiSandbox appliances in your environment, check their versions against Fortinet's advisories for these flaws, and upgrade to the fixed releases, prioritizing any internet-reachable or edge-facing devices.
Affected
Organizations running affected Fortinet FortiSandbox versions (CVE-2026-39808, CVE-2026-25089); unauthenticated attackers can run commands remotely, and active exploitation of FortiSandbox flaws has been reported, making unpatched appliances a real risk.
Fix
Upgrade FortiSandbox to the fixed versions, such as 4.4.9 for the April flaw, restrict and monitor management access to these appliances, and review logs and configurations for unauthorized commands or changes.

n8n token exchange flaw could let attackers log in as other users

A vulnerability in the workflow automation platform n8n could let an attacker log in as another user without their password. Tracked as CVE-2026-59208, the flaw sits in n8n's Enterprise token exchange feature, which lets embedded deployments avoid a second login by accepting tokens from partner identity providers. Because the code did not properly bind an identity to its issuer, a valid token from one issuer that carried the identifier of a user under a different issuer would log the attacker in as that user. n8n shipped a fix on June 24, and there is no evidence of exploitation. The bug was found by an AI penetration-testing agent.

Check
Check whether you run n8n, especially Enterprise deployments using the token exchange feature for embedding or single sign-on, confirm the version, and update to a release that includes the June fix.
Affected
Organizations running n8n Enterprise deployments that use the token exchange feature (CVE-2026-59208); a flaw in binding identities to issuers could let an attacker present a token and log in as another user.
Fix
Update n8n to a version containing the June 24 fix, review authentication logs for unexpected cross-issuer logins, and apply least privilege so that a single compromised account has limited reach.

Unpatched Shark vacuum flaw lets one stolen certificate control others region-wide

A researcher disclosed an unpatched flaw in internet-connected Shark robot vacuums that lets an attacker take control of other owners' units across the same cloud region. The certificate a vacuum uses to authenticate to its maker's Amazon cloud broker was never restricted to that one device, so a certificate pulled from a vacuum's flash memory can send root commands to any Shark vacuum the broker serves. That means watching the camera, driving the robot, reading the stored map of a home, and taking the Wi-Fi password in plaintext. No memory corruption or password guessing is needed. The researcher says the maker has had the report since March with no fix.

Check
If Shark robot vacuums are on your network, isolate them and other smart-home devices on a separate segment away from sensitive systems, keep their firmware current, and watch for the vendor's fix.
Affected
Owners of internet-connected Shark robot vacuums; an attacker with a certificate from one unit can run root commands on others region-wide, exposing camera feeds, home maps, and Wi-Fi passwords.
Fix
Isolate smart-home devices on their own network segment, limit what they can reach, and watch for the vendor to rescope its cloud certificate policy or reissue certificates, the real fix here.

Zoom patches critical flaw that could let attackers take over Windows accounts

Zoom has patched a critical vulnerability in its Windows software that could let an unauthenticated attacker take over user accounts over the network. Tracked as CVE-2026-53412 and rated 9.8, the flaw is an improper input validation issue affecting Zoom Workplace for Windows, the VDI client, and the Meeting SDK before version 7.0.0. Zoom found it internally, shared no technical details, and says there is no evidence of exploitation or public exploit code yet. Because the Windows client sits on millions of corporate desktops and the flaw needs no credentials or user interaction, it poses a broad risk, so applying the latest updates promptly is the key mitigation.

Check
Inventory where Zoom Workplace for Windows, the VDI client, or the Meeting SDK are deployed, check their versions, and roll out 7.0.0 or later, prioritizing widely used and internet-reachable systems.
Affected
Organizations and users running Zoom Workplace for Windows, the Windows VDI client, or the Windows Meeting SDK before version 7.0.0 (CVE-2026-53412); an unauthenticated network attacker could take over accounts without user interaction.
Fix
Update all affected Zoom Windows components to version 7.0.0 or later, apply the accompanying fixes for the related privilege-escalation flaws, and keep Zoom clients on automatic updates where possible.

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.

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.