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

Fortinet FortiMail zero-day under active exploitation allows unauthenticated arbitrary file writes

CISA added a critical FortiMail flaw to its Known Exploited Vulnerabilities catalog after reports of active exploitation. Tracked as CVE-2026-104286 and rated 9.8, it combines a path traversal with improper NULL byte neutralization, letting an unauthenticated attacker write arbitrary files on the underlying system through crafted HTTP or HTTPS requests. Fortinet confirmed in-the-wild exploitation. Affected versions are FortiMail 8.0.0 through 8.0.1, 7.6.0 through 7.6.6, 7.4.0 through 7.4.8, and 7.2.0 through 7.2.9, with fixed builds coming in the 8.0.2, 7.6.7, and 7.4.9 releases and a move off 7.2 to branch 7.4. Until fixes land for some versions, Fortinet recommends disabling IBE feature support and restricting access to the administrative interface.

Check
Identify internet-facing FortiMail appliances, apply the fixed release for your branch when available, and meanwhile disable IBE and restrict the admin interface.
Affected
FortiMail versions in the affected ranges let an unauthenticated attacker write arbitrary files via crafted web requests, and exploitation is already occurring.
Fix
Upgrade to the fixed FortiMail builds, apply the IBE and admin-access workarounds in the interim, and review hosts for unexpected written files.

Critical GitLab AI Gateway flaw lets authorized users run commands on self-hosted servers

GitLab disclosed a critical flaw in its AI Gateway, the service that connects a GitLab instance to AI models, that could let a logged-in user with Duo Agent Platform access run commands on the gateway under certain conditions. Tracked as CVE-2026-90970 and rated 9.9, it is fixed in gateway versions 19.2.4, 19.3.2, and 19.4.1. Only organizations that host their own gateway need to act; customers using a GitLab-hosted gateway are already fixed. GitLab strongly recommends self-hosted gateway operators update immediately and notified them before publishing. CISA's record currently lists exploitation as none.

Check
Determine whether your organization runs a self-hosted GitLab AI Gateway, and if so upgrade to 19.2.4, 19.3.2, or 19.4.1 immediately.
Affected
Self-hosted GitLab AI Gateways on affected versions let a logged-in user with Duo Agent Platform access run commands on the gateway server under certain conditions.
Fix
Update self-hosted gateways to the fixed versions, limit Duo Agent Platform access to trusted users, and monitor the gateway host for unexpected command execution.

Critical Dell storage module flaws grant unauthenticated admin access and root on Kubernetes nodes

Dell released updates for multiple critical flaws in Dell Container Storage Modules that could let attackers take over affected systems. CVE-2026-63688, rated 10.0, is missing authentication in the csm-authorization-storage gRPC server that an unauthenticated remote attacker could use to obtain storage backend administrator credentials for all registered arrays. CVE-2026-63692, also 10.0, lets an unauthenticated network attacker bypass authentication in the authorization proxy and tenant service to gain administrative privileges. CVE-2026-67269, rated 9.9, lets a low-privilege attacker escalate to root on cluster nodes, and CVE-2026-54472, rated 9.8, uses hard-coded credentials to forge valid administrative tokens. Together they expose storage credentials, cluster nodes, and the authorization layer in Kubernetes environments.

Check
Inventory Kubernetes clusters using Dell Container Storage Modules, apply Dell's fixed module versions promptly, and rotate storage backend credentials that may be exposed.
Affected
Kubernetes clusters running vulnerable Dell CSM versions expose storage admin credentials, allow authentication bypass, and permit escalation to root on cluster nodes.
Fix
Update Dell CSM modules, rotate storage array and token-signing credentials, restrict access to the CSM authorization services, and review cluster node integrity.

Attackers exploit Rejetto HTTP File Server session forgery flaw to gain code execution

VulnCheck reported active exploitation attempts against a critical Rejetto HTTP File Server flaw, CVE-2026-61500, rated 9.3. The vulnerability is session forgery stemming from a weak pseudo-random number generator: HFS 3.0.0 through 3.2.0 derives its session-cookie signing key from the non-cryptographic Math.random() generator and discloses outputs of the same generator to unauthenticated clients during login. A remote attacker can collect a small number of login responses, reconstruct the generator's state, recover the signing key, and forge a valid administrator session cookie. That yields full administrative access and remote code execution through the server_code configuration feature. Horizon3.ai described it as an authentication bypass enabling arbitrary code execution.

Check
Locate exposed Rejetto HFS 3.0.0 through 3.2.0 instances, update to a fixed release or take them off the public internet, and review for rogue admin sessions.
Affected
Rejetto HFS 3.0.0 through 3.2.0 lets a remote attacker recover the session signing key from login responses and forge an administrator cookie for code execution.
Fix
Patch or retire affected HFS instances, restrict access to trusted networks, and audit the server_code configuration and administrative sessions for abuse.

WordPress SC backdoor rebuilds itself from files database and shared memory after cleanup

Sucuri detailed a WordPress compromise using a backdoor it codenamed SC, after SC_ markers in the injected content, which it describes as a self-healing mesh. The payload lives in at least eight places at once, spread across files, the database, and a shared-memory segment, and every location can rebuild all the others. Cleaning every file on disk lets the next page load restore the whole set from the database or shared memory, so there is no single point to remove. The malware carries no readable function names, using a substitution cipher to unscramble its code, and a .user.ini auto_prepend_file runs a loader before every PHP request.

Check
Treat infected WordPress sites as needing coordinated full cleanup across files, database, and runtime, and rebuild from a known-good backup where feasible.
Affected
WordPress sites hit by the SC backdoor cannot be cleaned piecemeal, since files, database entries, and shared memory each regenerate the removed components.
Fix
Take the site offline during cleanup, purge all eight component types together, rotate credentials and keys, restore from clean backups, and harden PHP auto_prepend_file.

Citrix patches third exploited NetScaler zero-day causing denial of service in SAML deployments

Citrix released updates for a high-severity NetScaler flaw, CVE-2026-88779, rated 8.7, that has been exploited in targeted zero-day attacks. It is a memory overflow in NetScaler ADC and NetScaler Gateway that can cause denial of service under specific deployment conditions. Exploitation requires the appliance to be configured as a SAML service provider or SAML identity provider, which customers can confirm by checking their configuration for samlAction or samlIdPProfile entries. Fixed releases include 14.1-73.41 and later, 13.1-64.28 and later, and corresponding FIPS builds. This is the third exploited NetScaler zero-day disclosed in roughly two weeks, after the two remote code execution flaws Citrix confirmed in late September.

Check
Check NetScaler configurations for SAML service provider or identity provider entries, and upgrade affected ADC and Gateway deployments to the fixed releases now.
Affected
NetScaler ADC or Gateway configured as a SAML service provider or identity provider can be driven to denial of service by the memory overflow flaw.
Fix
Apply the fixed NetScaler releases, review SAML configuration exposure, and keep monitoring given repeated exploited zero-days against these appliances.

Official MCP Python SDK flaw lets malicious servers steal client OAuth credentials

The maintainers of the official Model Context Protocol Python SDK disclosed a flaw that lets a malicious MCP server trick an application built on the SDK into handing over the OAuth credentials it uses to log in to a real service. Affected versions sent the client secret, authorization code, and PKCE proof key to an attacker-controlled token endpoint, because the SDK did not always verify where the authorization server was. Cycode, which reported it, exchanged the stolen material for a valid access token carrying the app's permissions, and noted the long-lived client secret keeps working until rotated. Fixes are in versions 1.30.0 and 2.2.0.

Check
Upgrade the MCP Python SDK to 1.30.0 or 2.2.0, then rotate any OAuth client secrets that MCP clients may have sent to untrusted servers.
Affected
Applications built on affected MCP Python SDK versions can be induced by a malicious MCP server to leak their OAuth client secret, authorization code, and PKCE key.
Fix
Update the SDK, rotate exposed client secrets, and connect MCP clients only to servers whose authorization endpoints you trust and validate.

Apple patches exploited CoreGraphics zero-day enabling code execution from a malicious file

Apple released updates for a zero-day it says was used in extremely sophisticated targeted attacks against specific individuals on iOS versions before iOS 27. Tracked as CVE-2026-20700, the flaw is an out-of-bounds write in CoreGraphics, the framework for two-dimensional graphics, image rendering, and text drawing across iOS, macOS, iPadOS, watchOS, and tvOS, and was reported by Meta Product Security. Processing a maliciously crafted file can lead to arbitrary code execution, and Apple addressed it with improved bounds checking. The affected device list is broad, spanning iPhone 11 and later, many iPad models, and Macs running macOS Sequoia 15.8.1 and Tahoe 26.7.1. Apple did not attribute the attacks or name the targeted individuals.

Check
Push the latest iOS, iPadOS, and macOS updates to all managed Apple devices now, prioritizing individuals at elevated risk of targeted attacks.
Affected
Apple devices before the fixed versions can be driven to arbitrary code execution by opening a maliciously crafted file through the CoreGraphics out-of-bounds write.
Fix
Apply the CoreGraphics fixes across iOS, iPadOS, and macOS, enforce update deadlines via MDM, and consider Lockdown Mode for high-risk users.

Over 16,000 misconfigured Supabase databases expose personal data passwords and auth tokens

UpGuard found more than 16,000 misconfigured Supabase databases exposing readable tables with personally identifiable information, passwords, or authentication tokens, with a very small subset appearing to include credit card data. Supabase is an open-source PostgreSQL development platform, popular with developers using AI tools, which now account for more than 60 percent of newly created databases. UpGuard analyzed about 300,000 domains showing Supabase use and inferred exposed data types from table schemas. More than half of the exposed databases held PII, with a smaller subset exposing passwords and tokens. One US valet service alone exposed over 100,000 customer records, showing how missing access controls turn convenient backends into open data stores.

Check
Audit Supabase projects for tables readable without authentication, enable row-level security and proper policies, and rotate any exposed tokens or passwords.
Affected
Supabase projects deployed without row-level security or access policies expose their tables, leaking PII, credentials, and auth tokens to anyone who queries them.
Fix
Turn on row-level security, restrict anonymous access, review AI-generated backends for missing controls, and monitor for unauthorized table reads.

Carbonato botnet hijacks exposed Docker hosts to run a Telegram controlled AI agent

ThreatDown detailed Carbonato, a botnet that targets Docker daemons exposed without authentication on port 2375 and deploys the open-source Hermes Agent AI framework. It installs the framework unchanged, then overwrites its SOUL.md persona file with a 39-line prompt directing the agent to execute tasks received over Telegram, maintain persistence, and collect credentials. On each host it launches a privileged container to run commands on the underlying system, then scans neighboring networks every five minutes to spread further, giving it worm-like propagation. Researchers found the operation through an unauthenticated Docker registry publicly accessible since May, whose staged data included details of the botnet and a separate campaign distributing trojanized cryptocurrency wallet apps.

Check
Ensure no Docker daemon is exposed on port 2375 without authentication, restrict daemon access, and hunt hosts for Hermes Agent and rogue privileged containers.
Affected
Hosts running Docker daemons reachable without authentication on port 2375 can be taken over, run a Telegram-controlled AI agent, and be used to spread further.
Fix
Bind the Docker API to localhost or protect it with TLS and authentication, segment container hosts, and alert on unexpected privileged containers.