Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: unauthenticated-rce (32 articles)Clear

WordPress Core upgrade race condition draws nearly 63,000 code execution attempts in 24 hours

Wordfence blocked 62,969 attacks in 24 hours against a WordPress Core remote code execution flaw, rated 8.1 and tracked under GitHub advisory GHSA-4w3m-c66w-69mg with no CVE assigned. The flaw stems from predictable, web-accessible staging paths used during full-package core upgrades: new files, including the WordPress installer, are unpacked into a predictable wp-content/upgrade directory, and an unauthenticated attacker who requests the installer at the right moment can reach PHP code execution by winning a narrow race condition. It affects WordPress 4.7 through 7.1.3 and is fixed in 7.1.4, released October 28. Attackers are polling paths such as setup-config.php.

Check
Update WordPress Core to 7.1.4 now, and watch web logs for requests to wp-content/upgrade paths such as setup-config.php during and after upgrades.
Affected
WordPress sites on 4.7 through 7.1.3 expose a predictable upgrade staging path that an unauthenticated attacker can race to reach PHP code execution.
Fix
Apply WordPress 7.1.4, block external requests to wp-content/upgrade, and review sites for web shells or unexpected admin changes after the attack window.

Critical GitLab regex compiler flaw enables unauthenticated code execution across releases back to version 7.0

GitLab disclosed CVE-2026-110264, rated 10.0, which under certain conditions lets an unauthenticated user run arbitrary code on the server through an integer overflow while compiling a specially crafted regular expression. The flaw sits in Onigmo, the Ruby regex engine GitLab ships, and affects every release from 7.0 through 18.11 and the 19.x branches before their fixes, so it spans roughly twelve years of versions. Only self-managed installations must act; GitLab.com and Dedicated already run patched builds. Fixes are in 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, and 19.5.1. GitLab reports no exploitation yet.

Check
Upgrade self-managed GitLab to the fixed release for your branch, such as 18.11.13 or 19.5.1, immediately, since GitLab.com and Dedicated are already patched.
Affected
Self-managed GitLab from version 7.0 through the unpatched 18.11 and 19.x builds lets an unauthenticated user run code via a crafted regular expression under certain conditions.
Fix
Apply the fixed GitLab release, restrict who can submit regex-bearing pipeline input where possible, and monitor the server for unexpected code execution.

Critical FortiSIEM path traversal flaw gains public exploit enabling unauthenticated remote code execution

Fortinet patched CVE-2026-106173, a critical path traversal flaw rated 9.4 in FortiSIEM that lets an unauthenticated attacker execute commands through specially crafted packets, and researchers have now released a public proof of concept. The attacker connects to the gRPC service on TCP port 27918 and writes a file outside the intended directory, using a null byte in the query-id parameter to truncate the filename so the write lands on an existing path such as a Redis health-check script that cron runs every 60 seconds. FortiSIEM 7.5.0 is affected, 7.6 is not, and users should upgrade to 7.5.1 or above. Horizon3.ai published the research.

Check
Upgrade FortiSIEM 7.5.0 to 7.5.1 or above immediately, since a public proof of concept now exists, and restrict access to the gRPC service on port 27918.
Affected
FortiSIEM 7.5.0 lets an unauthenticated attacker write a file outside the intended directory through crafted packets to the gRPC service, achieving remote code execution via a cron-run script.
Fix
Apply the FortiSIEM 7.5.1 upgrade, restrict network access to the management and gRPC services, and review hosts for unexpected changes to cron-run scripts.

Drupal patches critical Field UI flaw opening an unauthenticated remote code execution path via contributed modules

Drupal patched CVE-2026-108097, a flaw in the Field UI module it rates 19 out of 25 on its own critical scale. Field UI built admin tables that ran each row's region callback through call_user_func_array without checking the callable, a path present since Drupal 8.9.0 in 2020, and the fix stops calling the callback. Several exploit paths run through contributed modules, and at least one needs no login, raising an unauthenticated remote code execution risk. Fixes are in 11.4.10, 11.3.19, and 10.6.19, with no fix for end-of-life branches. No exploit was public as of mid-October, but the team warned exploits could appear within hours.

Check
Update Drupal core to 11.4.10, 11.3.19, or 10.6.19, or uninstall the field_ui module until you can, and plan migration off end-of-life branches.
Affected
Drupal sites on affected or end-of-life versions expose a Field UI flaw with exploit paths through contributed modules, at least one requiring no authentication, risking remote code execution.
Fix
Apply the Drupal core fixes or disable field_ui, audit contributed modules for the vulnerable path, and prepare for rapid exploit development by monitoring and patching quickly.

Attackers exploit unauthenticated Bricksforge WordPress plugin flaw allowing arbitrary PHP upload and remote code execution

Patchstack detected active exploitation of CVE-2026-85097, a flaw rated 10.0 in the Bricksforge WordPress plugin, beginning October 7. The plugin does not validate the url field inside its temporaryFileUploads parameter, letting an unauthenticated attacker upload and execute arbitrary PHP code on vulnerable sites. Exploitation came from 63 unique source IPs, with six responsible for roughly 46 percent of requests. Versions up to and including 3.1.8.9 are affected; the vendor released a fix in 3.1.8.10, and the current release is 4.0.1. Wordfence published an advisory. Site operators should update immediately and check for unexpected PHP files and administrative changes.

Check
Update the Bricksforge plugin to at least 3.1.8.10, ideally 4.0.1, on all WordPress sites, then check for unexpected PHP files and new administrator accounts.
Affected
WordPress sites running Bricksforge up to 3.1.8.9 let an unauthenticated attacker upload and execute arbitrary PHP code, and exploitation has been underway since October 7.
Fix
Upgrade Bricksforge immediately, scan for web shells and unauthorized files, remove rogue admin accounts, rotate credentials and keys, and restrict access to the WordPress admin interface.

GitLab patches critical integer overflow in CI/CD regex compiler enabling unauthenticated remote code execution

GitLab disclosed CVE-2026-97229, a critical integer overflow in the CI/CD regular expression compiler that parses and evaluates regular expressions in pipeline configuration files. Under certain conditions, an unauthenticated user can execute arbitrary code on the GitLab server through a specially crafted regular expression. It affects versions from 19.2 before 19.2.8, 19.3 before 19.3.4, and 19.4 before 19.4.2, with fixes in 19.2.8, 19.3.4, and 19.4.2. Self-managed installations must upgrade immediately, while GitLab.com already runs the patched version and Dedicated customers need no action. A researcher reported it through GitLab's HackerOne program, and no exploitation is reported.

Check
Upgrade self-managed GitLab to 19.2.8, 19.3.4, or 19.4.2 immediately, since GitLab.com and Dedicated are already covered and no action is needed there.
Affected
Self-managed GitLab versions before the fixed releases let an unauthenticated user run arbitrary code on the server through a crafted regular expression in pipeline configuration.
Fix
Apply the fixed GitLab releases to self-managed installations, restrict who can submit pipeline configurations, and review the server for unexpected code execution.

Unpatched critical LMCache flaw lets unauthenticated attackers run code on exposed LLM cache servers

JFrog disclosed CVE-2026-105192, a critical flaw rated 9.8 in LMCache, open-source software that speeds up LLM servers such as vLLM. In multiprocess mode the cache runs as a standalone server reached over ZeroMQ with no authentication, and one message type is deserialized with pickle before its type is checked, letting a crafted message run code. The server is exposed only when an operator binds it to a routable address rather than the default localhost, and the code runs with LMCache's privileges, which are root in the project's official container images. No fix exists yet, and JFrog advises keeping the port on localhost or a trusted cluster network.

Check
Inventory LMCache deployments, confirm the ZeroMQ cache server is bound only to localhost or a trusted cluster network, and avoid exposing it on routable addresses until a fix ships.
Affected
LMCache 0.3.9 through 0.5.5 in multiprocess mode exposes an unauthenticated ZeroMQ socket that deserializes pickle data, letting a remote attacker run code as root on bound servers.
Fix
Keep the LMCache port on localhost or a trusted network, restrict network access to LLM cache hosts, and watch for an upstream patch since none is available yet.

Critical Bifrost AI gateway flaw lets unauthenticated attackers run commands and steal provider keys

JFrog disclosed a critical flaw in Bifrost, an open-source AI gateway routing to over twenty LLM providers, that lets an unauthenticated attacker run arbitrary commands on the gateway with a single HTTP request. Tracked as CVE-2026-90898 and rated 9.8, it affects all Bifrost HTTP transport versions before 2.1.0 when management authentication is disabled, which is the default. An attacker registers a stdio-type MCP client through an unauthenticated POST to /api/mcp/client, and Bifrost runs the command immediately, before any handshake, as the gateway user. Because the gateway stores API keys for every connected provider, command execution also exposes those credentials, and the official Docker image binds its management API to all interfaces.

Check
Upgrade Bifrost to transports 2.1.0, enable management authentication, keep the management listener off untrusted networks, and rotate any provider keys the gateway held.
Affected
Bifrost gateways before 2.1.0 with default disabled management auth let an unauthenticated attacker run commands and read every connected provider API key.
Fix
Update to 2.1.0, set governance.auth_config.is_enabled to true with strong credentials, avoid publishing the management port, and treat exposed instances as compromised.

SolarWinds Access Rights Manager hard coded key enables unauthenticated remote code execution

SolarWinds patched a high-severity flaw in Access Rights Manager, tracked as CVE-2026-28326 and rated 8.8, that stems from a hard-coded static key and can lead to unauthenticated remote code execution. The issue affects all Access Rights Manager 2026.2 and prior releases and is fixed in 2026.2.1. SolarWinds credited Armadin researcher Kai Huang and reported no evidence of exploitation in the wild. The advisory arrives alongside separate fixes: a Web Help Desk SAML authentication bypass, a Web Help Desk denial-of-service issue, and sixteen Serv-U flaws that could allow privilege escalation, code execution, and creation of administrator accounts.

Check
Inventory SolarWinds Access Rights Manager instances, confirm versions at or below 2026.2, and upgrade to 2026.2.1 on an emergency schedule.
Affected
Access Rights Manager 2026.2 and earlier ship a hard-coded static key that an unauthenticated attacker can use to reach remote code execution.
Fix
Patch to 2026.2.1, restrict management interfaces to trusted networks, and separately update Web Help Desk and Serv-U to their fixed builds.

Exploited Issabel PBX flaw uses a shared hardcoded key to run commands unauthenticated

Attackers are exploiting a critical flaw in Issabel Framework, the web interface for the open-source Asterisk-based phone system. Tracked as CVE-2026-89026 and scored 9.8, the flaw stems from a hardcoded token-signing key that is identical across every installation, so an unauthenticated attacker can forge a valid access token, call the system's call-origination endpoint, and make Asterisk run arbitrary operating-system commands. Researchers at VulnCheck flagged it, and the Shadowserver Foundation first saw exploitation on September 9. A patch released on August 1 replaces the shared key with a unique per-installation key. Exposed, unpatched phone systems should be treated as urgent given the low barrier to attack.

Check
Update Issabel Framework to the patched version that replaces the shared signing key, and take the phone system's web interface off the public internet, restricting it to trusted management networks.
Affected
Organizations running internet-exposed Issabel Framework phone systems (CVE-2026-89026); because the signing key is identical everywhere, an unauthenticated attacker can forge a token and run operating-system commands, and exploitation is underway.
Fix
Patch to remove the hardcoded key, restrict and monitor access to the PBX web and management interfaces, hunt for forged-token requests and unexpected command execution, and rotate credentials if compromise is suspected.