Rapid responses
The runZero Rapid Response program detects emerging threats and notifies you immediately. Older entries move to standalone queries or templates.
Apache HTTP Server is an open-source, cross-platform web server that serves web content by processing requests via the Hypertext Transfer Protocol (HTTP).
Certain versions of Apache HTTP Server are affected by a critical concurrency vulnerability in the mod_http2 module.
Improper synchronization in the assign_headers() function can lead to heap corruption and may allow remote code
execution (RCE). Only servers with mod_http2 enabled are exposed.
The following versions are affected:
- Apache HTTP Server: Versions 2.4.55 through 2.4.70
- mod_h2 (GitHub releases): Versions 2.0.8 through 2.0.42
_asset.protocol:http2 AND protocol:http2 AND (_service.product:"Apache:HTTPD:2.4.55" OR _service.product:"Apache:HTTPD:2.4.56" OR _service.product:"Apache:HTTPD:2.4.57" OR _service.product:"Apache:HTTPD:2.4.58" OR _service.product:"Apache:HTTPD:2.4.59" OR _service.product:"Apache:HTTPD:2.4.6_" OR _service.product:"Apache:HTTPD:2.4.70")
N-able N-central is an enterprise remote monitoring and management (RMM) software platform used by managed service providers (MSPs) and internal IT teams to discover, automate, patch, and secure network infrastructure and endpoints across Windows, macOS, Linux, and cloud environments.
An independent researcher has publicly disclosed numerous vulnerabilities in N-central under the name “Able2Shell”. CVE IDs have not yet been assigned. The researcher reports the following issue classes, among others:
-
Unauthenticated XML external entity (XXE) processing in the service-import function, chained with session confusion to achieve remote code execution as the
nableuser on N-central. -
Unauthenticated disclosure of customer asset-discovery database credentials, cross-customer appliance information, and reusable Ecosystem Agent credentials in N-central.
-
Unauthenticated overwrite of global configuration and remote-control records in N-central.
-
Stored cross-site scripting in the patch metadata view that leads to remote code execution, including as root through the Audit Export function, in N-central.
-
Authenticated command injection, file upload path traversal, and stack overflow vulnerabilities that lead to remote code execution, including as root, in N-central.
-
Missing authorization checks that allow low-privileged users to create Technician accounts, read appliance registration tokens, and write device configuration in N-central.
The researcher tested N-central appliance version 2026.4.0.31 and states that the issues are expected to affect earlier versions as well. These vulnerabilities have not been confirmed by runZero or by N-able.
N-able has published a status page about a critical security incident, describing it as a “public disclosure and non-responsible communication of critical vulnerabilities in N-central” found by an independent researcher. The page does not name the researcher, the Able2Shell disclosure, or any specific vulnerabilities, so it is likely, but not confirmed, to be related. N-able reports that it has not seen active exploitation and is developing a hotfix. N-able has taken its hosted N-central environments offline and advises on-premises customers to temporarily take their N-central servers offline until further guidance is provided. Details of the forthcoming fix are not yet available.
The following versions are affected:
- N-able N-central: Versions through 2026.4.0.31 are reported as affected; the full range of affected versions has not been confirmed.
vendor:="N-able" AND product:="N-central" AND source:runzero
SonicWall SonicOS is the operating system that manages the networking, routing, and security functions of SonicWall physical and virtual firewall appliances.
Certain versions of SonicOS on Gen7 and Gen8 firewalls are affected by multiple vulnerabilities:
-
CVE-2026-107155: A permissive cross-domain policy vulnerability in the SonicOS management interface could, under specific conditions, allow a remote, unauthenticated attacker to perform unauthorized operations.
-
CVE-2026-107154: A session validation vulnerability in the SonicOS management interface could, under specific conditions, allow a remote, unauthenticated attacker to perform unauthorized operations.
-
CVE-2026-82308: A pre-authentication heap-based buffer overflow in the SonicOS SSL-VPN service could allow a remote, unauthenticated attacker to cause an application-level denial of service.
-
CVE-2026-19868: An authentication enforcement vulnerability in the SonicOS SSLVPN service may allow a user with valid credentials for an alternate authentication method to bypass SAML authentication controls, including SAML-enforced multi-factor authentication (MFA). This vulnerability only affects SSLVPN when SAML is enabled for SSLVPN logins.
-
CVE-2026-77708: A pre-authentication stack-based buffer overflow in the SonicOS TACACS+ authentication client could, under specific conditions, allow a remote, unauthenticated attacker to cause an application-level denial of service.
-
CVE-2026-77709: A pre-authentication heap-based buffer overflow in the SonicOS TACACS+ authentication client could, under specific conditions, allow a remote, unauthenticated attacker to cause an application-level denial of service.
-
CVE-2026-19703: A weak password hashing vulnerability on SonicOS virtual appliances (NSv) could, under specific conditions, allow an attacker with existing local access to disclose a platform credential that provides access to a limited subset of platform settings.
Evidence indicates that CVE-2026-19868 is actively exploited in the wild, leading to its addition to the CISA Known Exploited Vulnerabilities (KEV) catalog on November 6, 2026.
The following versions are affected:
- SonicWall Gen7 Firewalls (TZ 270, TZ 270W, TZ 370, TZ 370W, TZ 470, TZ 470W, TZ 570, TZ 570W, TZ 570P, TZ 670, NSa 2700, NSa 3700, NSa 4700, NSa 5700, NSa 6700, NSsp 10700, NSsp 11700, NSsp 13700, NSsp 15700) and Gen7 NSv (NSv 270, NSv 470, NSv 870 on ESX, KVM, Hyper-V, AWS, and Azure): SonicOS 7.3.3-7015 and earlier.
- SonicWall Gen8 Firewalls (TZ 80, TZ 280, TZ 280W, TZ 380, TZ 380W, TZ 480, TZ 580, TZ 680, NSa 2800, NSa 3800, NSa 4800, NSa 5800) and Gen8 NSv (NSv XS, NSv S, NSv M, NSv L on ESX, KVM, Hyper-V, AWS, and Azure): SonicOS 8.2.2-8015 and earlier.
hw:="SonicWall%" AND os:="SonicWall SonicOS%" AND os_version:>0 AND ((os_version:>="7.0" AND os_version:<"7.3.4-7013") OR (os_version:>="8.0" AND os_version:<"8.2.3-8015"))
OpenSSH is a widely used implementation of the SSH protocol that provides secure remote login, command execution, and file transfer.
The sshd server in OpenSSH before 10.6p2 on Linux systems that use musl libc without PAM lacks a workaround for a
password authentication bypass. The bug stems from a misinterpretation of whether a string is intended to be a
password hash. On some account configurations, any password between 256 and 1024 characters succeeds, allowing a
remote, unauthenticated attacker to log in as an account that has no password set (for example, a key-only account
whose password field is *). Exploitation requires at least one other local account with a $5$ or $6$
password hash and PasswordAuthentication enabled, which is the default. Alpine Linux is an example of a platform
that uses musl libc without PAM in its default openssh-server package.
This query identifies Alpine Linux, OpenWrt, and Yocto systems with an OpenSSH service that offers password authentication. It does not confirm whether the installed package contains the fix.
Evidence indicates that this vulnerability is actively exploited in the wild, leading to its addition to the CISA Known Exploited Vulnerabilities (KEV) catalog on November 9, 2026.
The following versions are affected:
- OpenSSH: Versions prior to 10.6p2 on Linux systems using musl libc with PAM disabled
- Alpine Linux openssh: Versions prior to the fixed package for each release branch listed below, and
openssh-server-pamwithUsePAM no
(os:Alpine OR os:OpenWrt OR os:Yocto) AND _asset.protocol:ssh AND protocol:ssh AND ssh.authMethods:password AND _service.product:"OpenBSD:OpenSSH"
Barracuda Email Security Gateway (ESG) is a physical or virtual appliance that protects organizations from email-borne threats such as spam, phishing, malware, and data loss.
Certain versions of Barracuda Email Security Gateway are affected by multiple vulnerabilities:
-
CVE-2026-116606: An authentication bypass in Barracuda Email Security Gateway allows a remote attacker with network access to the administrative interface, without authenticating, to invoke a configuration-import function and restore a crafted, compatible backup archive, resulting in unauthorized modification of the appliance’s global configuration.
-
CVE-2026-111560: Improper neutralization of shell metacharacters in the timezone configuration field of Barracuda Email Security Gateway allows an authenticated administrator to inject OS commands that execute with root privileges when the crafted timezone value is subsequently processed.
When exploited in combination, these vulnerabilities allow an attacker with access to the administrative interface to bypass authorization controls and obtain root access to the appliance.
Evidence indicates that these vulnerabilities are actively exploited in the wild, leading to their addition to the CISA Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026.
The following versions are affected:
- Barracuda Email Security Gateway: Versions prior to 9.4.0.030 (CVE-2026-116606); versions through 9.4.0.27 (CVE-2026-111560)
hw:="Barracuda Email Security Gateway"
WordPress is an open source content management system used to build and manage websites, blogs, and web applications.
WordPress Core contains a race condition vulnerability in the core update process. During a core update that uses a complete package, WordPress extracts the new files to a predictable, web-accessible directory inside the upgrade folder. An unauthenticated attacker who wins a race against that extraction can execute arbitrary code on the server during the upgrade window.
Evidence indicates that this vulnerability is actively exploited in the wild, leading to its addition to the CISA Known Exploited Vulnerabilities (KEV) catalog on November 3, 2026.
The following versions are affected:
- WordPress 7.1: Versions 7.1.0 through 7.1.3
- WordPress 7.0: Versions 7.0.0 through 7.0.7
- WordPress 6.9: Versions 6.9.0 through 6.9.10
- WordPress 6.8: Versions 6.8.0 through 6.8.11
- WordPress 6.7: Versions 6.7.0 through 6.7.10
- WordPress 6.6: Versions 6.6.0 through 6.6.10
- WordPress 6.5: Versions 6.5.0 through 6.5.13
- WordPress 6.4: Versions 6.4.0 through 6.4.13
- WordPress 6.3: Versions 6.3.0 through 6.3.13
- WordPress 6.2: Versions 6.2.0 through 6.2.14
- WordPress 6.1: Versions 6.1.0 through 6.1.15
- WordPress 6.0: Versions 6.0.0 through 6.0.17
- WordPress 5.9: Versions 5.9.0 through 5.9.19
- WordPress 5.8: Versions 5.8.0 through 5.8.18
- WordPress 5.7: Versions 5.7.0 through 5.7.20
- WordPress 5.6: Versions 5.6.0 through 5.6.22
- WordPress 5.5: Versions 5.5.0 through 5.5.23
- WordPress 5.4: Versions 5.4.0 through 5.4.24
- WordPress 5.3: Versions 5.3.0 through 5.3.26
- WordPress 5.2: Versions 5.2.0 through 5.2.29
- WordPress 5.1: Versions 5.1.0 through 5.1.27
- WordPress 5.0: Versions 5.0.0 through 5.0.30
- WordPress 4.9: Versions 4.9.0 through 4.9.34
- WordPress 4.8: Versions 4.8.0 through 4.8.33
- WordPress 4.7: Versions 4.7.0 through 4.7.38
Severity & Risk Assessment
- Severity: High – Successful exploitation allows an unauthenticated remote attacker to execute arbitrary code on the web server, leading to full compromise of the hosted site and its data.
- Risk: Medium - The vulnerability requires no authentication or user interaction, but it is exploitable only while a core update is running and only by an attacker who wins the race against file extraction.
vendor:=WordPress AND product:=WordPress AND version:>0 AND ((version:>=7.1.0 AND version:<7.1.4) OR (version:>=7.0.0 AND version:<7.0.8) OR (version:>=6.9.0 AND version:<6.9.11) OR (version:>=6.8.0 AND version:<6.8.12) OR (version:>=6.7.0 AND version:<6.7.11) OR (version:>=6.6.0 AND version:<6.6.11) OR (version:>=6.5.0 AND version:<6.5.14) OR (version:>=6.4.0 AND version:<6.4.14) OR (version:>=6.3.0 AND version:<6.3.14) OR (version:>=6.2.0 AND version:<6.2.15) OR (version:>=6.1.0 AND version:<6.1.16) OR (version:>=6.0.0 AND version:<6.0.18) OR (version:>=5.9.0 AND version:<5.9.20) OR (version:>=5.8.0 AND version:<5.8.19) OR (version:>=5.7.0 AND version:<5.7.21) OR (version:>=5.6.0 AND version:<5.6.23) OR (version:>=5.5.0 AND version:<5.5.24) OR (version:>=5.4.0 AND version:<5.4.25) OR (version:>=5.3.0 AND version:<5.3.27) OR (version:>=5.2.0 AND version:<5.2.30) OR (version:>=5.1.0 AND version:<5.1.28) OR (version:>=5.0.0 AND version:<5.0.31) OR (version:>=4.9.0 AND version:<4.9.35) OR (version:>=4.8.0 AND version:<4.8.34) OR (version:>=4.7.0 AND version:<4.7.39))
runZero has identified multiple vulnerabilities in a large subset of major baseboard management controllers (BMCs) that can lead to device compromise or segmentation breakdowns. Details of individual vulnerabilities will be published as the disclosure process completes.
BMCs are embedded into every modern enterprise server. These devices run their own OS, have their own network interfaces, and are network-reachable even when the server is powered off. The devices speak a protocol called IPMI that was thoroughly trashed by Dan Farmer’s ground-breaking research in 2013. Since Farmer’s original research into Cipher Zero authentication bypass and RAKP password hash disclosure, dozens of new vulnerabilities have been identified in these devices, but none of this research revisits the IPMI protocol itself.
High level details of our findings will be presented at Black Hat 2026 & DEF CON 34.
(protocol:ipmi OR type:=BMC) AND ( hw:=OpenBMC OR hw:="Super Micro IPMI" OR hw:="HP% iLO%" OR hw:="Dell iDRAC%" OR hw:="AMI MegaRAC" OR (hw:="Raritan%" AND type:="Power Device") OR hw:="H3C HDM" OR hw:="Fujitsu%")
Each Rapid Response includes a query that finds matching assets, a trigger that analyzes all inventories for exposure, and a blog post with the details of the issue, so you can mitigate exposures before compromise.