# Rapid7 Cybersecurity

Rapid7 transforms data into insight, empowering security professionals to progress and protect their organizations.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## CVE-2026-123890: Critical Authentication Bypass in VMware vCenter

DevFeed: [CVE-2026-123890: Critical Authentication Bypass in VMware vCenter](<https://devfeed.tech/articles/cve-2026-123890-critical-authentication-bypass-in-vmware-vcenter-144830.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter>)

Author: Rapid7

Published: 2026-11-19T21:06:24Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [VMware Cloud Foundation](<https://devfeed.tech/topics/vcf-9-1.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [armory-castle](<https://devfeed.tech/tags/armory-castle.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [broadcom](<https://devfeed.tech/tags/broadcom.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123890](<https://devfeed.tech/tags/cve-2026-123890.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [in-the-wild-exploitation](<https://devfeed.tech/tags/in-the-wild-exploitation.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [mandiant](<https://devfeed.tech/tags/mandiant.md>), [mitigation](<https://devfeed.tech/tags/mitigation.md>), [network](<https://devfeed.tech/tags/network.md>), [patch](<https://devfeed.tech/tags/patch.md>), [security](<https://devfeed.tech/tags/security.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>), [server](<https://devfeed.tech/tags/server.md>), [threat](<https://devfeed.tech/tags/threat.md>), [vcenter](<https://devfeed.tech/tags/vcenter.md>), [vmware](<https://devfeed.tech/tags/vmware.md>), [vmware-vcenter](<https://devfeed.tech/tags/vmware-vcenter.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

CVE-2026-123890 is a critical, actively exploited authentication bypass in vCenter's VMware Directory Service. An attacker with network access can exploit it without credentials to gain Administrator access; Broadcom rates it CVSSv3 9.8, and Mandiant/Google Threat Intelligence reports ARMORY CASTLE exploitation as early as September 2026. Broadcom says systems below the fixed versions need this update even if they received the earlier, distinct CVE-2026-59309 fix. No workaround is listed, and Quick Patch cannot apply the fixes, so Broadcom calls for an emergency upgrade through the deployment's standard update mechanism. Updates temporarily make management interfaces unavailable, while running VM and container workloads continue. The 8.0 U3m and 9.0.2.0200 updates add a "Back-in-Time" restriction affecting upgrades to VMware Cloud Foundation 9.1.1; customers already upgrading are advised to consult Broadcom's FAQ and interoperability matrix.

### Source excerpt

Overview On November 19, 2026, Broadcom published VMware Security Advisory VMSA-2026-0009, addressing five vulnerabilities in VMware products. The most severe of these, CVE-2026-123890, is an authentication bypass using an alternate path or channel (CWE-288) in the VMware Directory Service component of vCenter. Broadcom assigned the vulnerability a critical CVSSv3 score of 9.8. A malicious actor with network access to an affected vCenter deployment may exploit CVE-2026-123890 without credentials to bypass authentication and gain unauthorized access to the system as the Administrator user. Mandiant privately reported the issue to Broadcom. Also, Mandiant/Google Threat Intelligence confirmed in-the-wild exploitation of CVE-2026-123890 by Chinese state-linked threat actor ARMORY CASTLE as early as September 2026. CVE-2026-123890 is distinct from the vCenter authentication bypass vulnerability CVE-2026-59309 that Broadcom addressed earlier in 2026. The vendor FAQ states that all vCenter systems below the versions fixed by VMSA-2026-0009 require the new update, including systems that already received the earlier fix. Broadcom characterizes the vCenter update as an emergency change requiring prompt action. Mitigation guidance Vendor-provided updates are available for CVE-2026-123890. Broadcom lists no workaround, and the patches cannot be applied using vCenter Quick Patch. Organizations should prioritize upgrading vCenter on an emergency basis, outside of normal patch cycles, using the standard update mechanism for their deployment. VMware Product Affected Version Fixed Version / Patch VMware Cloud Foundation / vSphere Foundation 9.1.x.x 9.1.1.0200 VMware Cloud Foundation / vSphere Foundation 9.0.x.x 9.0.2.0200 VMware vCenter Server 8.0 8.0 U3m VMware vCenter Server 7.0 Contact Broadcom Support (extended-support customers) VMware Cloud Foundation 5.x 5.2.5 VMware Telco Cloud Platform 3.0, 4.x, 5.0.x, 5.1.x, 5.2 8.0 U3m -- KB463116 VMware Telco Cloud Infrastructure 3.0 8.0

## What Is Preemptive MDR? A Guide For Security Leaders

DevFeed: [What Is Preemptive MDR? A Guide For Security Leaders](<https://devfeed.tech/articles/what-is-preemptive-mdr-a-guide-for-security-leaders-144829.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/dr-what-is-preemptive-mdr-security-leaders-guide>)

Author: Emma Burdett

Published: 2026-11-19T15:58:53Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [vulnerability management](<https://devfeed.tech/topics/vulnerability-management.md>), [threat detection](<https://devfeed.tech/topics/threat-detection.md>), [human review](<https://devfeed.tech/topics/human-review.md>)

Tags: [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [analysts](<https://devfeed.tech/tags/analysts.md>), [application](<https://devfeed.tech/tags/application.md>), [assets](<https://devfeed.tech/tags/assets.md>), [attack](<https://devfeed.tech/tags/attack.md>), [business](<https://devfeed.tech/tags/business.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [contain](<https://devfeed.tech/tags/contain.md>), [context](<https://devfeed.tech/tags/context.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [detection](<https://devfeed.tech/tags/detection.md>), [detection-and-response](<https://devfeed.tech/tags/detection-and-response.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [guide](<https://devfeed.tech/tags/guide.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-detection-and-response-mdr](<https://devfeed.tech/tags/managed-detection-and-response-mdr.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [mdr](<https://devfeed.tech/tags/mdr.md>), [mdr-must-haves](<https://devfeed.tech/tags/mdr-must-haves.md>), [security](<https://devfeed.tech/tags/security.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>), [what-is](<https://devfeed.tech/tags/what-is.md>)

### AI overview

Rapid7 describes preemptive MDR as connecting asset and vulnerability exposure context with threat intelligence, threat hunting, investigation, and response. Analysts use factors such as internet exposure, business criticality, and active exploitation to prioritize investigation and remediation; findings feed back into detection rules and hunting priorities, with ownership tracked through follow-up. AI can gather and correlate evidence and run parts of an investigation in parallel, but missing identity or asset data can leave gaps. Human analysts validate findings and weigh response consequences, such as disrupting a critical service. The article advises security leaders to ask providers to show how exposure context changes investigations, how identified weaknesses are assigned and addressed, what AI does and how it is overseen, and how responsibilities and approval for response actions are set. It says Rapid7 MDR includes unlimited incident response; progress should be reviewed through case evidence, including outstanding work.

### Source excerpt

When an MDR provider contains a compromised endpoint, your team needs to know whether the weakness that enabled the attack exists elsewhere and who is responsible for addressing it. Without that follow-through, the immediate incident may be resolved while another attacker still has a way in. Preemptive managed detection and response (MDR) is Rapid7's approach to connecting exposure context, threat intelligence, AI-assisted investigation, and human expertise. It supports proactive cybersecurity by helping teams prioritize weaknesses before exploitation, investigate threats with a clearer understanding of risk, and use their findings to strengthen defenses. How does preemptive MDR differ from traditional MDR? Managed detection and response provides security specialists who monitor, investigate, and respond to threats around the clock. Many services also include proactive threat hunting and recommendations to improve security. Preemptive MDR connects that work more directly to what makes an organization vulnerable. When analysts investigate suspicious activity on a server, knowing that it is internet-facing, supports a critical application, and has a vulnerability under active exploitation helps them assess urgency and determine where to look next. In Rapid7's model, exposure findings inform investigation and remediation priorities, while investigations reveal weaknesses that need attention. Security leaders gain a clearer connection between the threats their provider handles and the conditions their organization needs to address. Within a broader preemptive cybersecurity strategy, MDR connects exposure information with the people investigating and responding to threats. The aim is to reduce opportunities for compromise and intervene before an attack causes harm, while retaining the expertise to contain and recover from incidents. How exposure context and proactive threat hunting inform MDR By combining information about assets, vulnerabilities, business criticality, a

## Open by Default, Already Occupied: Threat Actors are Renting your Compute

DevFeed: [Open by Default, Already Occupied: Threat Actors are Renting your Compute](<https://devfeed.tech/articles/open-by-default-already-occupied-threat-actors-are-renting-your-compute-141103.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/tr-self-hosted-ai-renting-compute-exposed-servers>)

Author: Christiaan Beek

Published: 2026-11-18T14:38:55Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Self Hosted AI Tools](<https://devfeed.tech/topics/self-hosted-ai-tools.md>), [Ollama](<https://devfeed.tech/topics/ollama.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [OSINT](<https://devfeed.tech/topics/osint.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [22](<https://devfeed.tech/tags/22.md>), [abliterated-models](<https://devfeed.tech/tags/abliterated-models.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [alert](<https://devfeed.tech/tags/alert.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [compute](<https://devfeed.tech/tags/compute.md>), [conf](<https://devfeed.tech/tags/conf.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [internet](<https://devfeed.tech/tags/internet.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [more](<https://devfeed.tech/tags/more.md>), [open](<https://devfeed.tech/tags/open.md>), [other](<https://devfeed.tech/tags/other.md>), [people](<https://devfeed.tech/tags/people.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [shows](<https://devfeed.tech/tags/shows.md>), [snapshot](<https://devfeed.tech/tags/snapshot.md>), [threat](<https://devfeed.tech/tags/threat.md>), [threat-research](<https://devfeed.tech/tags/threat-research.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

A scan of 20,354 preselected internet-facing hosts found 7,714 unauthenticated AI or notebook API findings on 7,627 hosts, mostly Ollama. After filtering 429 likely deception hosts, the reported critical findings fell from 387 to 39, underscoring that exposure counts need qualification. Read-only Ollama model lists revealed apparent third-party activity: callback-style registry pulls, server IPs and markers in model names, and encoded paths targeting sensitive files. These artifacts indicate attempted access, not proof of successful exploitation; the scan sent no inference, write or exploit requests, and could not establish whether targets remained vulnerable. The article recommends inventorying public and personally expensed cloud/VPS systems, treating suspicious artifacts as compromise, rotating credentials and rebuilding, binding runtimes privately behind authentication, restricting egress, patching, logging state-changing API calls, and assigning each server an owner. The findings come from one snapshot of preselected IPv4 addresses and model-name indicators; clean lists do not establish a clean host.

### Source excerpt

A snapshot of 20,354 internet-facing hosts shows self-hosted AI deployed the way we deployed databases a decade ago. The more interesting part is what other people had already left inside.

## CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)

DevFeed: [CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)](<https://devfeed.tech/articles/cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed-141104.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed>)

Author: Stephen Fewer

Published: 2026-11-18T13:56:42Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [TLS (Transport Layer Security)](<https://devfeed.tech/topics/tls.md>), [Internet Traffic](<https://devfeed.tech/topics/internet-traffic.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [docker](<https://devfeed.tech/tags/docker.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [f5](<https://devfeed.tech/tags/f5.md>), [flow-control](<https://devfeed.tech/tags/flow-control.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [linux](<https://devfeed.tech/tags/linux.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [memory](<https://devfeed.tech/tags/memory.md>), [network](<https://devfeed.tech/tags/network.md>), [network-bandwidth](<https://devfeed.tech/tags/network-bandwidth.md>), [network-traffic](<https://devfeed.tech/tags/network-traffic.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [proof-of-concept](<https://devfeed.tech/tags/proof-of-concept.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [research](<https://devfeed.tech/tags/research.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-disclosure](<https://devfeed.tech/tags/vulnerability-disclosure.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

CVE-2026-123007 is a critical nginx HTTP/2 integer underflow that can enable unauthenticated code execution in the nginx worker under specific conditions. Rapid7's proof of concept worked on a Linux/amd64 nginx 1.31.8 Docker image with HTTP/2 and TLS enabled. The exploit cancels queued response data, causing nginx to restore flow-control credit above the HTTP/2 limit; a later unsigned subtraction underflows, and excessive credit becomes an invalid response length that can trigger out-of-bounds memory access during buffered TLS copying. Exploitation requires about 128 GB of HTTP/2 traffic in the overview; the analysis estimates about 119 GiB plaintext for the demonstrated route, plus TLS and network overhead. Bandwidth and nginx's default one-hour connection lifetime constrain feasibility, and proxied HTTP/2 frames may not preserve the required pattern. The demonstrated copy behavior also depends on a specific x86-64 glibc EVEX/YMM implementation and CPU features; other viable RCE methods are not known. Impact is limited to the worker's permissions. The excerpt says vendor fixes are available but does not identify versions or patch steps.

### Source excerpt

Overview Today, both Rapid7 and F5 are disclosing CVE-2026-123007, a critical integer underflow vulnerability affecting nginx HTTP/2, which can allow for unauthenticated remote code execution (RCE) against affected servers under certain conditions. CVE ID Description CWE CVSSv4 CVE-2026-123007 HTTP/2 flow-control memory corruption permitting worker-context RCE CWE-191 (Integer Underflow) 9.2 (Critical) nginx can miscalculate how much response data an HTTP/2 client has allowed it to send. A remote, unauthenticated client can exploit this error by cancelling queued response data, then make nginx use an invalid length when copying a later response. The resulting memory corruption can disclose data, interrupt service, and execute code with the nginx worker process's permissions. Impact Rapid7 has developed a proof-of-concept to demonstrate leveraging CVE-2026-123007 for unauthenticated RCE against a vulnerable linux/amd64 Docker image running nginx version 1.31.8, as shown below in Figure 1. The target nginx server's configuration had http2 on and TLS enabled. Note that for brevity, video playback is at 8x speed. Figure 1: Video demonstrating unauthenticated RCE against NGINX 1.31.8 via CVE-2026-123007 Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data. Both available network bandwidth and connection timeouts will place practical limitations on Internet exploitation. In the above example shown in Figure 1, exploitation takes two and a half minutes. The approximate timings to transmit the required network data over a 10 Gbit/s network is two minutes, while on a 1 Gbit/s network it is seventeen minutes. Due to nginx's default one hour connection lifetime, a network slower than approximately 300 Mbit/s will take over the one hour connection limit threshold and will not be able to succeed. Additionally, should an HTTP/2 connection be proxied, the precise attacker-controlled HTTP/2 frames

## Who Has Access to Claude? Bring AI Identity and Access Context Into Surface Command

DevFeed: [Who Has Access to Claude? Bring AI Identity and Access Context Into Surface Command](<https://devfeed.tech/articles/who-has-access-to-claude-bring-ai-identity-and-access-context-into-surface-command-138021.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/em-claude-access-brings-ai-context-into-surface-command-asm-easm>)

Author: Rapid7

Published: 2026-11-17T14:26:29Z

Content type: release

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [account](<https://devfeed.tech/tags/account.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-identity](<https://devfeed.tech/tags/ai-identity.md>), [api](<https://devfeed.tech/tags/api.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [assets](<https://devfeed.tech/tags/assets.md>), [basis](<https://devfeed.tech/tags/basis.md>), [breach](<https://devfeed.tech/tags/breach.md>), [can](<https://devfeed.tech/tags/can.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [claude](<https://devfeed.tech/tags/claude.md>), [command](<https://devfeed.tech/tags/command.md>), [context](<https://devfeed.tech/tags/context.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-and-access](<https://devfeed.tech/tags/identity-and-access.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [surface](<https://devfeed.tech/tags/surface.md>), [surface-command](<https://devfeed.tech/tags/surface-command.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Rapid7 Surface Command integrates with Claude's Compliance API to bring organization, user, role, group membership, and organizational settings information into a security platform for access reviews. Practitioners can inspect user roles and administrative status, follow user connections to the organization and groups in a relationship graph, and work with service owners to assess whether access still fits current responsibilities and policies; Surface Command provides context, while teams decide whether changes are needed. The integration is available through the Anthropic connector in the Rapid7 Extension Library and requires a Compliance API key and the appropriate Claude organization entitlement. It focuses on administrative visibility: it does not ingest conversation content, detect threats in Claude activity, or control Claude's behavior.

### Source excerpt

Approving an AI service is only the starting point. As employees adopt Claude and their responsibilities change, security teams need to know who has access, which users hold administrative privileges, and whether those roles and group memberships still reflect the work they do. IBM's 2025 Cost of a Data Breach Report found that, among studied organizations reporting an AI-related breach, 97% lacked proper AI access controls. The finding highlights a broader challenge: AI adoption needs security practices that extend beyond the initial approval, supported by information teams can use to review access with administrators and service owners. Rapid7 Surface Command now integrates with Claude's Compliance API, bringing supported organization, user, role, group, and settings information into the same platform teams use to understand other assets and identities. The integration helps security teams make enterprise Claude access part of their existing review practices. Bring enterprise AI access into your security view An account list tells security teams who is present, while roles and group memberships help explain how access is organized and where further review may be needed. Surface Command's integration with Claude's Compliance API brings together: Organizations and users: Visibility into the Claude organization and its associated user accounts. Roles and groups: Context to understand users' assigned roles and group memberships. Organizational settings: Available configuration information to support review of the enterprise Claude environment. With those details in Surface Command, practitioners can examine Claude identities alongside the other assets and identities they manage. That gives them a clearer basis for working with service owners to evaluate whether access remains appropriate as teams and responsibilities change. The integration focuses on administrative visibility. It does not ingest Claude conversation content, provide threat detection on Claude activity

## Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited

DevFeed: [Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited](<https://devfeed.tech/articles/rapid7-detected-exploitation-of-cve-2026-90436-against-atlassian-confluence-data-center-n-able-n-central-also-exploited-136439.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/etr-rapid7-detected-exploitation-of-cve-2026-90436-against-atlassian-confluence-data-center-n-able-n-central-also-exploited>)

Author: Rapid7

Published: 2026-11-16T18:14:14Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [atlassian](<https://devfeed.tech/topics/atlassian.md>), [Cybercrime](<https://devfeed.tech/topics/cybercrime.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [apache-software-foundation](<https://devfeed.tech/tags/apache-software-foundation.md>), [apis](<https://devfeed.tech/tags/apis.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [atlassian-confluence](<https://devfeed.tech/tags/atlassian-confluence.md>), [axis](<https://devfeed.tech/tags/axis.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [confluence-data-center](<https://devfeed.tech/tags/confluence-data-center.md>), [critical](<https://devfeed.tech/tags/critical.md>), [customer](<https://devfeed.tech/tags/customer.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [emerging-threats](<https://devfeed.tech/tags/emerging-threats.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [n-able](<https://devfeed.tech/tags/n-able.md>), [n-central](<https://devfeed.tech/tags/n-central.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

CVE-2026-90436 is an unauthenticated remote code execution flaw in end-of-life Axis 1.x, and exploitation has been reported against Atlassian Confluence Data Center and N-able N-central when specific non-default APIs are enabled. Rapid7 MDR detected Confluence exploitation on November 13, 2026; N-able separately reported N-central exploitation that strongly correlates with the CVE. Prioritize internet-facing systems with the relevant APIs enabled, check internal deployments, remediate urgently, and investigate exposed systems. For Confluence, upgrade to fixed 9.2.28 or an unaffected 10.x release; disabling Remote API can be a temporary measure, though integrations may break. N-central on-premises administrators should verify Legacy API is disabled and follow N-able's Agent and Probe upgrade guidance; hosted customers also need to follow that guidance. N-able says 2026.4 HF3 will permanently remove Legacy API access. Apache provides no fixed Axis 1.x release, recommending migration to another SOAP engine or a patched build.

### Source excerpt

Overview On November 6, 2026, the Apache Software Foundation disclosed CVE-2026-90436, a critical unsafe reflection vulnerability (CWE-470) in Axis 1.x that allows for unauthenticated remote code execution (RCE). Apache Axis is a Simple Object Access Protocol (SOAP) implementation used for the creation of Java Web services. CISA has assigned CVE-2026-90436 a CVSS score of 9.8 Critical. Since the initial November 6 disclosure, it has transpired that some versions of Atlassian Confluence Data Center and N-able N-central use the affected Axis library and are vulnerable to CVE-2026-90436. Both products require a non-default configuration in order to be vulnerable. CVE-2026-90436 is now being actively exploited in the wild against both known affected products. On November 13, 2026, Rapid7 MDR detected exploitation of CVE-2026-90436 against Atlassian Confluence Data Center in a customer environment. Separately, on November 13, 2026, N-able reported exploitation in the wild against N-central for a vulnerability that strongly correlates to CVE-2026-90436. A proof-of-concept exploit that leverages CVE-2026-90436 and targets N-central was published on November 12, 2026, as part of a series of public zero-day disclosures against N-central. Rapid7 recommends remediating exposed systems on an emergency basis outside of normal patching cycles. Mitigation guidance Prioritize internet-accessible instances with the relevant APIs enabled, and check internal deployments as well. Apply the product-specific actions below, then investigate systems that were exposed for evidence of compromise. Axis 1.x through 1.4 is affected but has reached end of life (EOL) and Apache does not plan to publish a fixed Axis 1.x release. Apache recommends moving to another SOAP engine (for example, Apache Axis 2) or using an Axis 1.x build with this patch applied. Organizations using products that are affected by this issue should follow the product vendor's specific remediation instructions. Atlassian Con

## From view-only access to container root: five vulnerabilities in ONLYOFFICE Docs (FIXED)

DevFeed: [From view-only access to container root: five vulnerabilities in ONLYOFFICE Docs (FIXED)](<https://devfeed.tech/articles/from-view-only-access-to-container-root-five-vulnerabilities-in-onlyoffice-docs-fixed-136440.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ve-from-view-only-access-to-container-root-five-vulnerabilities-in-onlyoffice-docs-fixed>)

Author: Jonah Burgess

Published: 2026-11-16T16:24:38Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [onlyoffice](<https://devfeed.tech/tags/onlyoffice.md>), [rapid7-disclosure](<https://devfeed.tech/tags/rapid7-disclosure.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [root](<https://devfeed.tech/tags/root.md>), [view](<https://devfeed.tech/tags/view.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-disclosure](<https://devfeed.tech/tags/vulnerability-disclosure.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Rapid7 reports five vulnerabilities in ONLYOFFICE Docs, demonstrated on Document Server 9.4.0-129: a view-only user could chain flaws to execute commands as root inside the official container, and could retrieve document data the viewer did not see even when downloading was disabled. The chains exploit DocBuilder authorization and unsafe conversion parameters or complete-save path handling, then use a passwordless root helper with injectable sed input. A separate view-only export flaw lets a reconnecting session replace its callback and invoke sendForm. An unauthenticated WOPI entry is conditional on WOPI being enabled, the attacker source being reachable, and its address passing the configured filter. The tested findings were fixed in Document Server 10.0.0-169: fixes restrict DocBuilder tokens and conversion fields, enforce storage boundaries, validate the helper argument, and restrict sendForm and callback replacement. The broader affected-version range is unknown; upgrade to version 10.0 or later.

### Source excerpt

Overview As part of our research into Zimbra Collaboration Suite, Rapid7 reported five findings in ONLYOFFICE Docs. An attacker with view-only access to a document can chain vulnerabilities in ONLYOFFICE Docs to execute arbitrary operating system commands as root inside the official DocumentServer container. The findings also expose server files and document data that the viewer never displays, even when downloading is disabled. CVE Finding CVSS CVE-2026-113627 DocBuilder native file read and Session JWT forgery 7.1 High CVE-2026-110385 DocBuilder SaveFile conversion parameter injection and code execution 8.7 High CVE-2026-97727 Complete-save format path traversal and arbitrary file write 6.5 Medium CVE-2026-113630 Root-helper command injection 7.8 High CVE-2026-113631 View-only export of non-rendered document data 6.5 Medium ONLYOFFICE confirmed on October 23, 2026 that all five findings were fixed in Document Server 10.0. The changelog describes the release's security changes. Proof-of-concept code is available on the accompanying Github repository. Product description ONLYOFFICE Docs provides online viewers and editors for documents, spreadsheets, presentations, forms and PDFs. It supports collaborative editing and can integrate with applications that store and share files. An integrating application, for example Zimbra Collaboration Suite, supplies an opening configuration identifying the document and the user's permissions, signed with the Browser key. This client-visible credential is referred to below as the Editor JWT. After opening a document, DocumentServer issues a Session JWT for reconnecting and saving. Incoming service requests, including document-building jobs, are validated using ONLYOFFICE's Inbox JWT key. DocumentServer can also send generated document output to the integrating application's callback URL. Credit This assessment and the exploit-chain research were conducted by Jonah Burgess (CryptoCat), Senior Security Researcher at Rapid7. The find

## MDR Pricing: Comparing Asset-Based and Ingestion-Based Costs

DevFeed: [MDR Pricing: Comparing Asset-Based and Ingestion-Based Costs](<https://devfeed.tech/articles/mdr-pricing-comparing-asset-based-and-ingestion-based-costs-133511.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/dr-mdr-pricing-comparing-asset-ingestion-based-ingestion-costs>)

Author: Emma Burdett

Published: 2026-11-13T16:37:29Z

Content type: comparison

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [also](<https://devfeed.tech/tags/also.md>), [analysts](<https://devfeed.tech/tags/analysts.md>), [approach](<https://devfeed.tech/tags/approach.md>), [asset](<https://devfeed.tech/tags/asset.md>), [assets](<https://devfeed.tech/tags/assets.md>), [based](<https://devfeed.tech/tags/based.md>), [budget](<https://devfeed.tech/tags/budget.md>), [budgeting](<https://devfeed.tech/tags/budgeting.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [charges](<https://devfeed.tech/tags/charges.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compare](<https://devfeed.tech/tags/compare.md>), [comparison](<https://devfeed.tech/tags/comparison.md>), [contribute](<https://devfeed.tech/tags/contribute.md>), [costs](<https://devfeed.tech/tags/costs.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [detection-and-response](<https://devfeed.tech/tags/detection-and-response.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-detection-and-response-mdr](<https://devfeed.tech/tags/managed-detection-and-response-mdr.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [mdr](<https://devfeed.tech/tags/mdr.md>), [mdr-must-haves](<https://devfeed.tech/tags/mdr-must-haves.md>), [pricing](<https://devfeed.tech/tags/pricing.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Compare MDR proposals using the same asset inventory, data sources, retention needs, response expectations, and annual budget; then make exclusions, operational consequences, and growth assumptions explicit. Asset-based pricing ties charges to a defined asset population, so clarify asset counts, included sources and services, integration limits, and extra charges. Ingestion-based pricing depends partly on collected or processed data volume, so check allowances, billable-volume measurement, overage effects, and retention or search costs. Compare the full technology, analyst, investigation, and response scope: a SIEM ingestion fee alone is not equivalent to an MDR subscription. Rapid7 defines an asset as a supported physical or virtual endpoint or server and states that MDR includes 13 months of hot log storage. Keyloop's reported increase in ingestion and retention illustrates possible visibility and history differences, but does not establish comparable cost savings. The text recommends testing a relevant threat scenario in a proof of concept and modeling changes such as acquisitions, added workloads, or new log sources. It notes Rapid7 renewal uplifts are capped at 5% for the term

### Source excerpt

When comparing MDR pricing, it helps to understand what the same annual budget would buy from each provider. Two proposals with similar prices may give analysts access to different evidence, retain it for different periods, or leave your team with different responsibilities. Those differences can affect what happens when you need to investigate a compromised account or trace an attacker's low-and-slow activity across your environment. For security leaders weighing asset-based against ingestion-based pricing, a useful comparison starts with the systems you need to protect and the logs required to investigate threats. Giving providers the same requirements and budget helps expose the decisions behind each quote, including what you would need to exclude or pay more to include. Asset-based vs. ingestion-based MDR pricing Under asset-based pricing, the charge is tied to a defined population of assets. You need to establish how the provider counts workstations, servers, cloud resources, and other systems, alongside which data sources and service capabilities the price includes. A predictable asset count can help with budgeting, but the proposal still needs to explain any integration limits or additional service charges. At Rapid7, an asset is defined as any physical or virtual endpoint or server running a supported operating system within the monitored environment. With ingestion-based pricing, some of the cost depends on the volume of data collected or processed. The comparison needs to account for the included allowance, how billable volume is measured, and what happens when usage increases. Retention, search, and supporting infrastructure may also contribute to the overall cost, depending on the commercial model. At Rapid7, MDR customers have access to 13 months hot storage of logs as standard. Whichever approach you are evaluating, include the technology, analysts, and response support needed to deliver the service. A SIEM ingestion charge on its own cannot be compare

## Patch Tuesday - November 2026

DevFeed: [Patch Tuesday - November 2026](<https://devfeed.tech/articles/patch-tuesday-november-2026-128015.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/em-patch-tuesday-november-2026>)

Author: Adam Barnett

Published: 2026-11-10T21:55:37Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [microsoft 365](<https://devfeed.tech/topics/microsoft-365.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [classic-outlook](<https://devfeed.tech/tags/classic-outlook.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-124194](<https://devfeed.tech/tags/cve-2026-124194.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [file](<https://devfeed.tech/tags/file.md>), [hash](<https://devfeed.tech/tags/hash.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [ntlm](<https://devfeed.tech/tags/ntlm.md>), [outlook](<https://devfeed.tech/tags/outlook.md>), [patch-tuesday](<https://devfeed.tech/tags/patch-tuesday.md>), [patching](<https://devfeed.tech/tags/patching.md>), [security](<https://devfeed.tech/tags/security.md>), [spoofing](<https://devfeed.tech/tags/spoofing.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

The excerpt reports 1,092 Microsoft product vulnerabilities for November 2026 Patch Tuesday, including 1,102 in Windows, and says Microsoft knows of in-the-wild exploitation for one vulnerability. CVE-2026-124194 affects classic Outlook: opening a specially crafted malicious file can silently connect to an attacker-controlled location and leak the user's NTLM v2 hash. The text notes that the large rise in vulnerability volume has not been accompanied by a rise in known in-the-wild exploitation, and questions whether patching more flaws will improve security outcomes given the possibility of new bugs. The excerpt ends mid-sentence, so it does not establish the full affected-version scope or remediation details.

### Source excerpt

Microsoft is publishing 1,092 own-product vulnerabilities on November 2026 Patch Tuesday, including 1,102 vulnerabilities in Windows. Until a few months ago, these volumes would have been unimaginable, but if anything, this month feels like a slight reprieve. The jury is still out on whether patching many more vulnerabilities will lead to better security outcomes; every code change to resolve a known vulnerability could easily introduce new hidden treasure for researchers or threat actors to unearth in the future. Despite the vast uptick in volume during 2026, there has been no accompanying increase in the number of vulnerabilities known to be exploited in the wild. Microsoft is aware of exploitation in the wild for just one of the vulnerabilities published today, with no known public disclosure at all this month. Outlook: zero-day spoofing Imagine coming home and checking your mailbox to find a postcard. You admire the non-specific image of a tropical beach at sunset, and flip it over to scan the handwriting on the back, which looks vaguely familiar. It's addressed to you, but you can't make out the signature, and the message is short and generic. Is that real handwriting, or has this been printed? Probably marketing material. You put the card in the recycling and, since life is busy, you move on and forget about it. Somehow, you remain entirely unaware that, immediately after reading the postcard, you took out your phone and sent high-resolution images of your front door key to a number you've never contacted before. Is this sketch just some rather questionable science fiction? Yes, hopefully, but what if that non-specific postcard was instead a malicious file in your Outlook inbox? Now we're talking about CVE-2026-124194, an exploited-in-the-wild spoofing vulnerability. Merely opening a specially crafted malicious file causes Outlook to silently connect to an attacker-controlled location and leak the user's NTLM v2 hash. All supported versions of classic Outlook

## Critical vulnerabilities in N-able N-central prompt hosted shutdown

DevFeed: [Critical vulnerabilities in N-able N-central prompt hosted shutdown](<https://devfeed.tech/articles/critical-vulnerabilities-in-n-able-n-central-prompt-hosted-shutdown-126839.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/etr-critical-vulnerabilities-in-n-able-n-central-prompt-hosted-shutdown>)

Author: Rapid7

Published: 2026-11-10T14:20:34Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [availability](<https://devfeed.tech/tags/availability.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [combines](<https://devfeed.tech/tags/combines.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [covering](<https://devfeed.tech/tags/covering.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [critical](<https://devfeed.tech/tags/critical.md>), [customer](<https://devfeed.tech/tags/customer.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [emerging-threats](<https://devfeed.tech/tags/emerging-threats.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [n-able](<https://devfeed.tech/tags/n-able.md>), [n-central](<https://devfeed.tech/tags/n-central.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

N-able advised keeping N-central deployments offline while it develops and validates a hotfix after public disclosure of 33 issues with proof-of-concept code, including unauthenticated remote code execution, root privilege escalation, credential disclosure, and unauthorized account creation. One reported chain uses XML external entity and session-handling weaknesses to execute code as the nable service account. As of November 10, N-able reported scanning tied to the PoC but no evidence of successful customer exploitation; hosted N-central classic environments remained offline. Rapid7 recommends taking on-premises servers offline until a hotfix is available and successfully installed, following vendor restoration updates for hosted service, and checking servers and downstream systems for compromise. The excerpt reports testing on Appliance 2026.4.0.31, but N-able had not specified the full affected-version range, a fixed build, CVE identifiers, or CVSS scores.

### Source excerpt

Overview On November 9, 2026, N-able announced that it was responding to the public disclosure of critical vulnerabilities affecting N-central, its remote monitoring and management (RMM) platform. In a public disclosure titled Able2Shell, an independent researcher has published details and proof-of-concept (PoC) code covering 33 issues. According to the disclosure, the issues include unauthenticated remote code execution (RCE), privilege escalation to root, credential disclosure, and unauthorized account creation. One unauthenticated chain combines XML external entity (XXE) and session-handling weaknesses to execute code as the nable service account. Other demonstrated chains involve an administrator viewing malicious patch metadata or use ProductAdmin credentials. Rapid7 Intelligence is currently triaging the newly published details. As of November 10, N-able reported scanning activity associated with the published PoC code and said it had no evidence that any customer environment had been successfully exploited. The vendor has advised keeping N-central deployments offline while it develops and validates a hotfix. Hosted N-central classic environments remain offline, according to the same notice. N-able's notice does not yet include CVE identifiers or CVSS scores. N-central is used by managed service providers (MSPs) and enterprise IT teams to administer endpoints and infrastructure. Compromise of an RMM server can put downstream managed environments at risk. N-central has previously been targeted through separate vulnerabilities, including an authentication bypass covered by Rapid7 in August 2026. Given the platform's administrative reach and the availability of public exploit code, Rapid7 recommends treating the current disclosure as an emergency. Mitigation guidance Rapid7 strongly recommends that organizations operating on-premises N-central servers take them offline immediately and keep them offline until the hotfix is available, and the server has been succes

## Five Signs Your MDR is All Alert, No Action

DevFeed: [Five Signs Your MDR is All Alert, No Action](<https://devfeed.tech/articles/five-signs-your-mdr-is-all-alert-no-action-126840.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/five-signs-your-mdr-is-all-alert-no-action>)

Author: Rapid7

Published: 2026-11-10T14:04:31Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [alert](<https://devfeed.tech/tags/alert.md>), [assets](<https://devfeed.tech/tags/assets.md>), [budget](<https://devfeed.tech/tags/budget.md>), [charts](<https://devfeed.tech/tags/charts.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [detection](<https://devfeed.tech/tags/detection.md>), [detection-and-response](<https://devfeed.tech/tags/detection-and-response.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [false-positives](<https://devfeed.tech/tags/false-positives.md>), [incident](<https://devfeed.tech/tags/incident.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-detection-and-response-mdr](<https://devfeed.tech/tags/managed-detection-and-response-mdr.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [mdr](<https://devfeed.tech/tags/mdr.md>), [mdr-must-haves](<https://devfeed.tech/tags/mdr-must-haves.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

The excerpt suggests MDR may be shifting investigation work back to your analysts when alerts arrive without context, recurring false positives persist, or the provider does not account for asset importance, identity access, vulnerabilities, and current threats. It recommends checking whether investigations lead to better detections or response plans, clarifying which response activities and hours are included and what triggers extra charges, and tracing a closed case from initial signal through evidence, ruled-out activity, actions, and team involvement. Bring real alerts and investigations to a service review and ask what the provider investigated, did, and improved.

### Source excerpt

Your managed detection and response (MDR) provider flags suspicious activity, and your analyst spends the next hour finding the account, checking logs, and deciding whether anything needs to happen. By the time the investigation is underway, the alert feels less like help and more like a task assignment. MDR should bring your team capacity and expertise when it needs them. If the service keeps handing the hardest work back to your analysts, these five signs can help you work out where the arrangement is falling short. 1. Every alert arrives with homework If your analysts are still sorting through the same recurring false positives, the extra coverage may be creating more work than it removes. Even an alert worth investigating is only so useful when your team has to gather the basic context before it can make a decision. Take a few recent alerts and look at what your provider had already checked when it contacted you. You should be able to see how it separated routine activity from a credible threat, and what it did to stop familiar noise from coming back. 2. It spots the fire, but cannot see the fuel A suspicious login involving an account with broad access deserves a different response from the same activity on a tightly restricted account. The systems within reach, their importance to the business, and any known weaknesses all help determine what needs attention first. When your MDR leaves your team to assemble that picture during an investigation, valuable time goes into finding context that could have informed the response from the start. Find out how your provider uses information about assets, identities, vulnerabilities, and current threats, including what it can help you address before an incident occurs. 3. Your team gets incident updates, but few useful lessons When a provider contains a threat and closes the case, your team should come away with more than a record of what happened. Consider the last significant investigation: did it lead to a clearer dete

## Metasploit Wrapup: Unauth RCE modules in Network Perimeter Devices and much more

DevFeed: [Metasploit Wrapup: Unauth RCE modules in Network Perimeter Devices and much more](<https://devfeed.tech/articles/metasploit-wrapup-unauth-rce-modules-in-network-perimeter-devices-and-much-more-121387.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/pt-metasploit-wrapup-unauth-rce-modules-in-network-perimeter-devices-and-much-more>)

Author: Jack Heysel

Published: 2026-11-06T13:52:11Z

Content type: release

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Regular expression](<https://devfeed.tech/topics/regular-expression.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-secure-email](<https://devfeed.tech/tags/cisco-secure-email.md>), [citrix](<https://devfeed.tech/tags/citrix.md>), [citrix-netscaler](<https://devfeed.tech/tags/citrix-netscaler.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [devices](<https://devfeed.tech/tags/devices.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-ci](<https://devfeed.tech/tags/gitlab-ci.md>), [integer-overflow](<https://devfeed.tech/tags/integer-overflow.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [metasploit](<https://devfeed.tech/tags/metasploit.md>), [metasploit-weekly-wrapup](<https://devfeed.tech/tags/metasploit-weekly-wrapup.md>), [modules](<https://devfeed.tech/tags/modules.md>), [network](<https://devfeed.tech/tags/network.md>), [products-and-tools](<https://devfeed.tech/tags/products-and-tools.md>), [rce](<https://devfeed.tech/tags/rce.md>), [release](<https://devfeed.tech/tags/release.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

This Metasploit Framework release adds unauthenticated RCE modules for Citrix NetScaler and Cisco Secure Email Gateway, plus GitLab CI/CD RCE requiring credentials with write access to a public project. Other additions include Flowise account takeover through a password reset token exposed in the API response, SPIP password changes without an authorization check, and OpenBullet2 RCE and NTLMv2 hash disclosure affecting releases from 0.2.5 onward. Portainer's module requires valid credentials and access to a managed Docker environment to run a command as host root. The release also adds LoongArch64 fetch payloads and Windows AArch64 SMB payload generation, alongside Docker persistence support on Windows and assorted scanner, cleanup, dependency, and documentation fixes. The supplied text describes the listed release changes; it does not establish broader coverage.

### Source excerpt

Buckle up Metasploit-Framework enthusiasts because we have another action packed release for you. I'm talking, unauthenticated remote code execution modules in some of the biggest names in network perimeter devices like Citrix NetScaler and Cisco Secure Email Gateway. That's not all, we have an authenticated GitLab CI/CD regular expression integer overflow RCE module that was recently making head lines among many other awesome exploit modules. Looking for auxiliary modules?

## Gartner Report: The Attack Path is Closing Faster than Most Teams Can Patch

DevFeed: [Gartner Report: The Attack Path is Closing Faster than Most Teams Can Patch](<https://devfeed.tech/articles/gartner-report-the-attack-path-is-closing-faster-than-most-teams-can-patch-119225.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ai-gartner-report-attack-paths-closing-faster-than-patchable>)

Author: Rapid7

Published: 2026-11-05T14:00:00Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [also](<https://devfeed.tech/tags/also.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [attack](<https://devfeed.tech/tags/attack.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [business](<https://devfeed.tech/tags/business.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [change](<https://devfeed.tech/tags/change.md>), [combined](<https://devfeed.tech/tags/combined.md>), [comes](<https://devfeed.tech/tags/comes.md>), [connect](<https://devfeed.tech/tags/connect.md>), [contain](<https://devfeed.tech/tags/contain.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [faster](<https://devfeed.tech/tags/faster.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [patch](<https://devfeed.tech/tags/patch.md>), [report](<https://devfeed.tech/tags/report.md>), [teams](<https://devfeed.tech/tags/teams.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

The excerpt argues that frontier AI can make it faster to turn separate weaknesses into executable attack paths, so security teams should judge progress by reduced enterprise risk and response speed rather than vulnerability counts alone. It cites measures such as attack path analysis coverage, patching and compensating control deployment cadence, mean time to remediate, and technology debt. Gartner recommends using attack path analysis to prioritize patches, virtual patches, and compensating controls in the context of critical services and business outcomes. The text says teams still need to identify affected systems, apply business context, choose and verify remediation, and maintain detection coverage. Rapid7 describes its capabilities as combining exposure visibility, threat intelligence, business context, and attack path analysis; the excerpt does not provide comparative product evaluations.

### Source excerpt

Security teams have never lacked vulnerability data. The harder problem is deciding which issues create a credible path to business impact, then acting before that path can be used. As frontier AI makes it faster and less expensive to connect weaknesses, operational assumptions, and legitimate system behavior, that decision window is becoming even tighter. The Gartner® report, Mythos Reprioritizes Cybersecurity Outcomes and Investments, examines what this shift means for cybersecurity priorities and investment. Rapid7 is offering complimentary access to the research, which we believe can help security leaders reassess how they prioritize exposure and infrastructure teams reassess how they plan response and recovery. Why does AI change the vulnerability management equation? Gartner states, "Mythos collapses the distance between theoretical weaknesses and executable attack scenarios, forcing cybersecurity to optimize for outcomes, not activity." For leaders already managing more vulnerabilities than their teams can address, the pressure comes from the growing speed at which separate weaknesses can become a credible attack path. The change also extends beyond one model. Gartner states, "By 2027, Mythos will be overtaken by new frontier-AI-enabled models, signaling that this moment is not about Mythos, but a new era of AI-assisted vulnerabilities and functional exploits." At Rapid7, we believe this requires a more attacker-aware view of exposure. A large backlog can contain thousands of issues with very different implications for the organization. Leaders need to understand which exposures are reachable, how they could be combined, which business services they affect, and what action would reduce risk most effectively. What should security leaders measure instead? Vulnerability counts, backlog size, and generic remediation targets show how much work a team has completed. They provide less clarity on whether an attacker's options have narrowed or whether the organization

## Rapid7 Achieves ISO/IEC 42001 Certification for its AI Management System

DevFeed: [Rapid7 Achieves ISO/IEC 42001 Certification for its AI Management System](<https://devfeed.tech/articles/rapid7-achieves-iso-iec-42001-certification-for-its-ai-management-system-119226.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ai-iso-iec-42001-certification-achieved>)

Author: Rapid7

Published: 2026-11-04T16:25:55Z

Content type: release

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [responsible-ai](<https://devfeed.tech/topics/responsible-ai.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [ai regulation](<https://devfeed.tech/topics/ai-regulation.md>), [Shared Responsibility Model](<https://devfeed.tech/topics/shared-responsibility-model.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-products](<https://devfeed.tech/tags/ai-products.md>), [ai-systems](<https://devfeed.tech/tags/ai-systems.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [audit](<https://devfeed.tech/tags/audit.md>), [audits](<https://devfeed.tech/tags/audits.md>), [certification](<https://devfeed.tech/tags/certification.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-command](<https://devfeed.tech/tags/exposure-command.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [governance](<https://devfeed.tech/tags/governance.md>), [human-oversight](<https://devfeed.tech/tags/human-oversight.md>), [in-the-loop](<https://devfeed.tech/tags/in-the-loop.md>), [information-security](<https://devfeed.tech/tags/information-security.md>), [iso](<https://devfeed.tech/tags/iso.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-detection-and-response-mdr](<https://devfeed.tech/tags/managed-detection-and-response-mdr.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [nist](<https://devfeed.tech/tags/nist.md>), [products](<https://devfeed.tech/tags/products.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [regulations](<https://devfeed.tech/tags/regulations.md>), [risk-assessment](<https://devfeed.tech/tags/risk-assessment.md>), [security](<https://devfeed.tech/tags/security.md>), [transparency](<https://devfeed.tech/tags/transparency.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Rapid7 says its AI Management System has received ISO/IEC 42001:2023 certification after an independent audit by Schellman Compliance, an ANAB-accredited certification body. The standard covers organizational AI governance, including risk assessment, data management, production monitoring, human oversight and accountability. Certification is maintained through annual surveillance audits. Its stated scope includes seven AI systems in Rapid7 products, including an MDR workflow that supports Rapid7's own SOC analysts. Rapid7 presents the certification as audited evidence that can support customer governance and vendor reviews, while emphasizing that it does not replace customer due diligence: Rapid7 is responsible for designing, building and operating the in-scope systems, and customers control how they use AI outputs in their security operations.

### Source excerpt

Exciting news for AI governance! Rapid7 has achieved ISO/IEC 42001:2023 certification for our Artificial Intelligence Management System (AIMS). The certificate was issued by Schellman Compliance, LLC, an ANAB accredited certification body, following an independent audit of how we govern the AI systems we develop in our role as an AI provider. What is ISO/IEC 42001? ISO/IEC 42001 is the first international management system standard for artificial intelligence. Where ISO/IEC 27001 focuses on information security, ISO/IEC 42001 focuses on how an organization governs AI. What exactly does "governing AI" mean? Essentially, it means how AI risks and impacts are assessed, how data is managed, how systems are monitored once they're in production, and how humans stay in the loop across the AI lifecycle. This certification means an accredited third party has audited our AIMS and confirmed that it aligns to the standard. To note, this isn't a one-time exercise, as the certification is maintained through annual surveillance audits. This means our AI governance program is held to the standard for as long as the certificate is active. Why is ISO/IEC 42001 certification important? AI is continually evolving how security teams work, and it's also causing teams to reconsider the questions they ask their vendors. Where does the model come from? What data does it use? Who reviews its outputs? How do we maintain the integrity and quality of our AI products? ISO/IEC 42001 certification gives customers independent evidence that Rapid7 has a management system in place to address those questions. It demonstrates that the in-scope AI systems are developed and operated under a structured program covering risk assessment, transparency, human oversight, and accountability. It also supports customers in their own governance work. Many organizations are building AI risk into their third party risk programs and preparing for frameworks and regulations such as the NIST AI Risk Management Framewor

## The Race Against the 3-Day Clock: How Rapid7 Helps Meet BOD 26-04 Compliance

DevFeed: [The Race Against the 3-Day Clock: How Rapid7 Helps Meet BOD 26-04 Compliance](<https://devfeed.tech/articles/the-race-against-the-3-day-clock-how-rapid7-helps-meet-bod-26-04-compliance-116610.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/it-racing-the-three-day-clock-cisa-bod-26-04>)

Author: Rapid7

Published: 2026-11-04T14:01:55Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [audit](<https://devfeed.tech/topics/audit.md>), [Finance](<https://devfeed.tech/topics/finance.md>)

Tags: [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [air-gapped](<https://devfeed.tech/tags/air-gapped.md>), [bod-26-04](<https://devfeed.tech/tags/bod-26-04.md>), [breach](<https://devfeed.tech/tags/breach.md>), [bug](<https://devfeed.tech/tags/bug.md>), [clock](<https://devfeed.tech/tags/clock.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-score](<https://devfeed.tech/tags/cvss-score.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [data-breach-investigations-report](<https://devfeed.tech/tags/data-breach-investigations-report.md>), [defer](<https://devfeed.tech/tags/defer.md>), [directives](<https://devfeed.tech/tags/directives.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exploited-vulnerabilities](<https://devfeed.tech/tags/exploited-vulnerabilities.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [forensic](<https://devfeed.tech/tags/forensic.md>), [framework](<https://devfeed.tech/tags/framework.md>), [full](<https://devfeed.tech/tags/full.md>), [government](<https://devfeed.tech/tags/government.md>), [hiring](<https://devfeed.tech/tags/hiring.md>), [industry-trends](<https://devfeed.tech/tags/industry-trends.md>), [internet](<https://devfeed.tech/tags/internet.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

BOD 26-04 replaces fixed vulnerability deadlines with risk-based remediation tiers using public exposure, KEV status, exploit automation and technical impact. For Tier 1 vulnerabilities (KEV-listed and granting total control), agencies must remediate within three days and investigate for compromise in parallel; volatile evidence should be captured before patching can overwrite it. Isolation, mitigation or uninstalling vulnerable software can count as remediation, and reducing public exposure can relax the timeline. The directive applies to Federal Civilian Executive Branch agencies and can reach contractors and cloud providers through agency contracts. The article maps Rapid7 products to these needs: Surface Command for asset exposure, InsightVM and Active Risk for vulnerability prioritization, Exposure Command AI for unscored CVEs, and Velociraptor for endpoint evidence collection and IOC hunts. These are the article's proposed capabilities; the excerpt does not provide the remediation-tier table or case-study details.

### Source excerpt

Introduction to BOD 26-04 On June 10, 2026, CISA issued Binding Operational Directive 26-04, "Prioritizing Security Updates Based on Risk." Strip away the regulatory language and it reads like a single operational fact: for a vulnerability that is actively exploited, publicly reachable, and grants an attacker full control, you now have three calendar days to remediate it -- and you must run a forensic investigation in parallel to determine whether you've already been breached. The 2026 Verizon Data Breach Investigations Report puts the industry's median full-remediation time at 43 days, adding that only 26% of Known Exploited Vulnerabilities were fully remediated in 2025, down from 38% the year before. That's a 43-day reality vs. a 3-day mandate; a gap you don't exactly just close by hiring more workers. This blog aims to break down what BOD 26-04 actually requires, mapping each point to the Rapid7 capability that helps to make compliance operationally achievable for all. What did CISA actually change? BOD 26-04 supersedes and revokes two prior directives: BOD 19-02 (2019), which prioritized internet-facing vulnerabilities by static CVSS score, and BOD 22-01 (2021), which created the Known Exploited Vulnerabilities (KEV) Catalog but applied a 14-day patch deadline to every entry regardless of context. Note that flat timeline: under BOD 22-01, an actively exploited bug on an air-gapped internal server carried the same 14-day urgency as one on a public-facing web server granting full admin control. Teams burned cycles patching low-risk systems to satisfy a checklist. BOD 26-04 replaces that with a dynamic model: prioritize what attackers are actually exploiting, and formally defer what they aren't. The four variables to BOD 26-04 BOD 26-04 abandons CVSS as the sole trigger and evaluates every vulnerability against four binary variables, derived from the SSVC decision framework (CMU CERT/CC and CISA): Asset Exposure: Is the asset reachable by untrusted entities over a p

## Additional Ivanti Connect Secure zero-days exploited in the wild (CVE-2026-111357, CVE-2026-118527)

DevFeed: [Additional Ivanti Connect Secure zero-days exploited in the wild (CVE-2026-111357, CVE-2026-118527)](<https://devfeed.tech/articles/additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527-112187.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/etr-additional-ivanti-connect-secure-zero-days-exploited-in-the-wild-cve-2026-111357-cve-2026-118527>)

Author: Rapid7

Published: 2026-11-02T11:04:08Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Security](<https://devfeed.tech/topics/security.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>)

Tags: [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [connect-secure](<https://devfeed.tech/tags/connect-secure.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [days](<https://devfeed.tech/tags/days.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [emerging-threats](<https://devfeed.tech/tags/emerging-threats.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [file-upload](<https://devfeed.tech/tags/file-upload.md>), [ivanti](<https://devfeed.tech/tags/ivanti.md>), [kev](<https://devfeed.tech/tags/kev.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [privilege-escalation](<https://devfeed.tech/tags/privilege-escalation.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [security-advisory](<https://devfeed.tech/tags/security-advisory.md>), [upload](<https://devfeed.tech/tags/upload.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>), [zero](<https://devfeed.tech/tags/zero.md>), [zero-days](<https://devfeed.tech/tags/zero-days.md>)

### AI overview

Ivanti Connect Secure flaws CVE-2026-111357 and CVE-2026-118527 were exploited in the wild in a chain with the authentication bypass CVE-2026-104935; Ivanti says a limited number of customers were affected. Fixes are available for all three. Ivanti rates the privilege escalation flaw 8.8 and the authenticated file upload flaw 4.3, while CVE records and Rapid7 rate the former 7.0 based on different attack-complexity and scope assumptions. Volexity observed root access, credential theft and Active Directory queries; it warns that the activity evades Ivanti's Integrity Checker Tool. Rapid7 recommends emergency updates and post-patch compromise investigation. Ivanti advises upgrading 22.8.X to 25.1.1.3 or later, or applying 22.8R2.6 if migration is delayed. Preserve memory and logs before rebooting or resetting when feasible; suspected compromises warrant Ivanti's recovery steps and credential rotation. The excerpt also provides appliance evidence locations, a network IOC and request patterns for hunting.

### Source excerpt

Overview On October 29, 2026, Ivanti updated its security advisory for Ivanti Connect Secure (ICS) to include two additional vulnerabilities and released fixes for both. Ivanti rates CVE-2026-111357, a missing authentication for critical function vulnerability (CWE-306), with a CVSSv3.1 score of 8.8; it allows a local authenticated attacker to escalate privileges. CVE-2026-118527, classified as generation of predictable numbers or identifiers (CWE-340), has an Ivanti-assigned CVSSv3.0 score of 4.3 and, according to CISA's KEV entry, allows a remote authenticated attacker to upload attacker-controlled content to a known location on disk. Per Ivanti, exploitation in the wild has already occurred prior to disclosure, affecting a limited number of customers when these flaws are chained with CVE-2026-104935, an authentication bypass by spoofing (CWE-290). Rapid7 covered the original disclosure on October 13, 2026, when a fix for CVE-2026-104935 was available but the privilege escalation component remained unpatched. Fixes are now available for all three vulnerabilities. On October 30, 2026, CVE-2026-111357 and CVE-2026-118527 were added to the U.S. Cybersecurity and Infrastructure Security Agency's (CISA) list of known exploited vulnerabilities (KEV), based on evidence of active exploitation. The following scores and classifications are from Ivanti's updated advisory: CVE Ivanti CVSS score CWE Impact CVE-2026-104935 8.6 (High), CVSSv3.0 CWE-290 Remote unauthenticated command execution CVE-2026-111357 8.8 (High), CVSSv3.1 CWE-306, CWE-862, CWE-345 Local authenticated privilege escalation CVE-2026-118527 4.3 (Medium), CVSSv3.0 CWE-340 Remote authenticated file upload to a known path Note: The CVE record and Rapid7's vulnerability database rate CVE-2026-111357 at 7.0, using high attack complexity and unchanged scope. Ivanti assesses low attack complexity and changed scope, resulting in its score of 8.8. The table follows Ivanti's scores and classifications. In its investiga

## Rapid7 Analysis: Unauthenticated File Upload to RCE in BeyondTrust Remote Support (CVE-2026-102764)

DevFeed: [Rapid7 Analysis: Unauthenticated File Upload to RCE in BeyondTrust Remote Support (CVE-2026-102764)](<https://devfeed.tech/articles/rapid7-analysis-unauthenticated-file-upload-to-rce-in-beyondtrust-remote-support-cve-2026-102764-109847.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ra-rapid7-analysis-unauthenticated-file-upload-to-rce-in-beyondtrust-remote-support-cve-2026-102764>)

Author: Jack Heysel

Published: 2026-10-30T16:01:53Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Tool](<https://devfeed.tech/topics/tool.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [file](<https://devfeed.tech/topics/file.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>)

Tags: [beyondtrust](<https://devfeed.tech/tags/beyondtrust.md>), [cve-2026-102764](<https://devfeed.tech/tags/cve-2026-102764.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [metasploit](<https://devfeed.tech/tags/metasploit.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [rapid7-analysis](<https://devfeed.tech/tags/rapid7-analysis.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [rce](<https://devfeed.tech/tags/rce.md>), [upload](<https://devfeed.tech/tags/upload.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

An origin-validation flaw in BeyondTrust Remote Support 24.1.2 (build 1524046) lets an unauthenticated customer session forge a reserved local router ID. The appliance's thin-scc worker then accepts the message as local and exposes its native file-transfer service. On the tested appliance, an attacker could choose uploaded file contents and destination, write PHP into the public document root, and execute it as msfuser (UID 1000); the described Metasploit module automates this chain. The test had public issue-menu session starts and thin chat enabled. The excerpt does not establish other affected releases or fixed builds. It describes possible detection clues, including unexpected PHP files and correlated HTTP, thin-scc, and brain logs, while cautioning that normal session activity, generic errors, and individual log entries do not prove exploitation.

### Source excerpt

Overview An origin-validation flaw in BeyondTrust Remote Support lets an unauthenticated attacker write files on the appliance and execute code as the site's operating-system user. The entry point is the public customer connection used to start a support session. No account credentials or user interaction are required. The flaw sits between the internal message router, brain, and an appliance-side customer worker, thin-scc. An attacker can put a reserved local router ID into a message's source address. The router forwards the message, and the worker accepts that address as proof that the request came from a local component. This gives the attacker access to an internal file-transfer service, including its native filesystem provider. We first confirmed the file write then used the primitive to upload a PHP file to the site's public directory. Requesting that file gave us code execution as the site user. A Metasploit module now implements the chain with PHP and Unix Command targets. We tested Remote Support 24.1.2, build 1524046, revision 4208-ddcf90715106aa0c0e19c103f8d2c412af4beff3. The test appliance had public issue-menu session starts and thin chat enabled (default). Other affected releases and fixed builds have not been established. The VM's base appliance version of Secure Remote Access, 7.1.0, is separate from the Remote Support application version. Impact The attacker controls both the contents of an uploaded file and its destination path, subject to the worker's filesystem permissions. The same origin forgery also reaches the file-send operation. We used it to retrieve /proc/self/environ to determine the base installation path of the Remote Support before dropping the payload On the tested appliance, the native file service could write into the PHP document root. The Metasploit module returns code execution in the context of msfuser, UID 1000, which establishes unauthenticated remote code execution as the site user. Technical Analysis We will demonstrate how

## How Rapid7 InsightGovCloud Supports BOD 22-01 Compliance

DevFeed: [How Rapid7 InsightGovCloud Supports BOD 22-01 Compliance](<https://devfeed.tech/articles/how-rapid7-insightgovcloud-supports-bod-22-01-compliance-104500.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/pt-insightgovcloud-supports-bod-22-01-compliance>)

Author: Rapid7

Published: 2026-10-28T13:16:39Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [vulnerability scanning](<https://devfeed.tech/topics/vulnerability-scanning.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [audit](<https://devfeed.tech/topics/audit.md>)

Tags: [active-directory](<https://devfeed.tech/tags/active-directory.md>), [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [assets](<https://devfeed.tech/tags/assets.md>), [automated](<https://devfeed.tech/tags/automated.md>), [aws](<https://devfeed.tech/tags/aws.md>), [azure](<https://devfeed.tech/tags/azure.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-environments](<https://devfeed.tech/tags/cloud-environments.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-and-infrastructure-security-agency](<https://devfeed.tech/tags/cybersecurity-and-infrastructure-security-agency.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [enumerate](<https://devfeed.tech/tags/enumerate.md>), [environment](<https://devfeed.tech/tags/environment.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [government](<https://devfeed.tech/tags/government.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [products-and-tools](<https://devfeed.tech/tags/products-and-tools.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

InsightGovCloud supports BOD 22-01 workflows through continuous asset discovery, KEV prioritization, remediation tracking, and reporting. InsightVM uses Discovery Connections to poll sources such as Active Directory, AWS, and Azure and launch scans; InsightCloudSec inventories new cloud resources and assesses them against compliance frameworks. Rapid7 says its KEV inventory covers 90% of on-premise and cloud host vulnerabilities. The suite ingests CISA's KEV catalog, helps triage findings and assign remediation work to teams against organization-defined timelines, and provides dashboards to track progress. It also offers CyberScope XML exports for submissions and an audit trail. The source describes these as product capabilities and does not establish that using the suite alone ensures compliance.

### Source excerpt

An introduction to CISA's BOD 22-01 Issued nearly four years ago, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) Binding Operational Directive 22-01 (BOD 22-01) has been adopted across both public and private sector organizations as a framework to ensure timely remediation of vulnerabilities being exploited by adversaries. By establishing a catalog of known exploited vulnerabilities (KEVs) and emphasizing a risk-based, prioritized approach, it provides a clear model for organizations to strengthen their cybersecurity posture and reduce exposure to real-world threats. InsightGovCloud, Rapid7's FedRAMP-authorized suite of security solutions, helps organizations implement BOD 22-01 by providing automated vulnerability scanning, real-time alerts for KEVs, and reporting aligned with regulatory requirements. Public and private sector teams can quickly identify at-risk assets, prioritize remediation efforts based on active exploitation, and maintain an auditable record of compliance. By leveraging our secure, cloud-based platform, organizations gain continuous visibility, streamlined vulnerability management, and the confidence that remediation aligns with federal cybersecurity standards. How InsightGovCloud stacks up against key BOD 22-01 requirementsRequirement 1: Maintain continuous inventory and visibility InsightVM, included in the suite, supports continuous and automated discovery of both external and internal assets through Discovery Connections, which allow organizations to continuously poll network sources like Active Directory, AWS, and Azure to enumerate connected hosts and launch scans. For cloud environments, Rapid7 InsightCloudSec will continuously inventory the entire environment for the creation of new resources and automatically scan and assess those resources against compliance frameworks. Rapid7 also maintains up-to-date inventory of CISA KEVs with an industry leading 90% coverage for both on-premise and cloud based host vulnerabilities

## Simplify User Access Management with SCIM on Rapid7 Command Platform

DevFeed: [Simplify User Access Management with SCIM on Rapid7 Command Platform](<https://devfeed.tech/articles/simplify-user-access-management-with-scim-on-rapid7-command-platform-102401.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/pt-scim-simplifies-user-access-management-uam-command-platform>)

Author: Michael Chroney

Published: 2026-10-27T12:24:04Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [okta](<https://devfeed.tech/topics/okta.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [administration](<https://devfeed.tech/tags/administration.md>), [applications](<https://devfeed.tech/tags/applications.md>), [automate](<https://devfeed.tech/tags/automate.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [command](<https://devfeed.tech/tags/command.md>), [complex](<https://devfeed.tech/tags/complex.md>), [control](<https://devfeed.tech/tags/control.md>), [customers](<https://devfeed.tech/tags/customers.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [employee](<https://devfeed.tech/tags/employee.md>), [employee-lifecycle](<https://devfeed.tech/tags/employee-lifecycle.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [identity-access-management-iam](<https://devfeed.tech/tags/identity-access-management-iam.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [management](<https://devfeed.tech/tags/management.md>), [platform](<https://devfeed.tech/tags/platform.md>), [product-updates-news](<https://devfeed.tech/tags/product-updates-news.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [user](<https://devfeed.tech/tags/user.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Rapid7 Command Platform supports SCIM to automate user lifecycle management through an organization's existing identity provider. It can create accounts, synchronize supported user attributes and group membership, and deactivate accounts when access is no longer needed, reducing repetitive administration and the chance of stale accounts. Administrators configure SCIM in Command Platform's SSO settings; it is disabled by default and must be configured before provisioning starts. The source says setup prerequisites and instructions are available in the Command Platform SCIM integration documentation.

### Source excerpt

Managing access to security tools shouldn't require another manual process. As organizations grow, keeping user accounts and permissions up to date becomes increasingly complex. Employees join, change roles, and leave, creating a constant need to update access across applications. When these processes rely on manual administration, delays and oversights can introduce unnecessary work and security risk. Rapid7 Command Platform now supports System for Cross-domain Identity Management (SCIM), enabling customers to automate user provisioning and deprovisioning through their existing identity provider (IdP). This helps organizations reduce administrative overhead, maintain more consistent access controls, and manage identity at scale. Automate user access throughout the employee lifecycle SCIM is an open standard that enables identity providers, such as Okta, to automatically manage user accounts in connected applications. With SCIM enabled, Rapid7 Command Platform customers can: Automate provisioning: Create accounts when employees join or need access. Keep user information current: Synchronize supported user attributes as information changes. Simplify offboarding: Automatically deactivate accounts when users no longer require access. Manage groups at scale: Synchronize group membership to help streamline access administration. Rather than manually updating accounts in Command Platform, administrators can manage supported identity lifecycle changes through their existing IdP. Less administration, more consistent access control Consider a common scenario: An employee leaves the organization. Without automated provisioning, an administrator must remember to deactivate that employee's access across their applications. If an account is missed, it could remain active longer than intended. With SCIM, changes made in the organization's identity provider can automatically trigger corresponding account updates in Command Platform. By introducing SCIM at the platform level, Rapid

## CVE-2026-111497: Critical out-of-bounds write in the Node.js Brotli decoder

DevFeed: [CVE-2026-111497: Critical out-of-bounds write in the Node.js Brotli decoder](<https://devfeed.tech/articles/cve-2026-111497-critical-out-of-bounds-write-in-the-node-js-brotli-decoder-100764.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/etr-cve-2026-111497-critical-out-of-bounds-write-in-the-node-js-brotli-decoder>)

Author: Rapid7

Published: 2026-10-26T17:32:46Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [brotli-decoder](<https://devfeed.tech/tags/brotli-decoder.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [crash](<https://devfeed.tech/tags/crash.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-111497](<https://devfeed.tech/tags/cve-2026-111497.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [data](<https://devfeed.tech/tags/data.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [emerging-threats](<https://devfeed.tech/tags/emerging-threats.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [google](<https://devfeed.tech/tags/google.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [memory](<https://devfeed.tech/tags/memory.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [out-of-bounds-write](<https://devfeed.tech/tags/out-of-bounds-write.md>), [rapid7](<https://devfeed.tech/tags/rapid7.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remediation](<https://devfeed.tech/tags/remediation.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

CVE-2026-111497 is an out-of-bounds write in Google Brotli, bundled in Node.js 22.x, 24.x and 26.x. When an application decompresses attacker-controlled Brotli data with node:zlib, malformed input can overrun an eight-byte decoder buffer and corrupt process memory, potentially causing a crash, memory disclosure or remote code execution. Upgrade to Node.js 22.23.4+, 24.22.1+ or 26.12.1+; end-of-life lines should be treated as affected and migrated to a supported fixed line. Node.js provides no supported workaround. If an upgrade is not immediately possible, Rapid7 recommends restricting or disabling paths that decompress untrusted Brotli data. Other products also bundle affected Brotli implementations, but versions and exposure vary; consult their vendor or distribution advisories. Rapid7 reported no known in-the-wild exploitation as of October 26, 2026.

### Source excerpt

Overview On October 21, 2026, the Node.js Project published a security advisory for CVE-2026-111497, an out-of-bounds write in the Brotli decoder bundled with Node.js. The vulnerability affects the Node.js 26.x, 24.x, and 22.x release lines. Node.js rates the issue High, while Google, the CVE Numbering Authority (CNA), gives it a critical CVSSv4 score of 9.2. An attacker who can supply Brotli data that an application decompresses with node:zlib can corrupt process memory. According to Node.js, this corruption can lead to a process crash, disclosure of sensitive process memory, or remote code execution. Exposure therefore depends on whether an application passes attacker-controlled compressed data to the affected decoder. As of October 26, 2026, Rapid7 is not aware of exploitation in the wild, and CVE-2026-111497 is not listed in CISA's Known Exploited Vulnerabilities catalog. However, given the vulnerability's potential to disclose memory or enable remote code execution (RCE), Rapid7 recommends that organizations prioritize remediation. Technical overview CVE-2026-111497 is classified as an out-of-bounds write (CWE-787) and an unchecked return value (CWE-252). Per the vendor advisory, the decoder handled an invalid Brotli block switch as a temporary need for more input instead of a permanent format error. The streaming decoder then continued appending input bytes to an eight-byte internal buffer, allowing malformed input to write beyond the buffer and corrupt process memory. The vulnerability originates in Google Brotli, which the affected Node.js release lines bundle as a dependency. The CVE record identifies affected upstream Brotli ranges on all platforms as versions 1.0.3 before 1.0.10, 1.1.0 before 1.1.1, and 1.2.0 before 1.2.1. The Node.js Project remediated its bundled decoder in the fixed Node.js releases listed below. Because CVE-2026-111497 affects the upstream Google Brotli decoder, its reach is not limited to Node.js. Vendor and project advisories have a

## Metasploit Wrap Up: Langflow, MongoDB, and More

DevFeed: [Metasploit Wrap Up: Langflow, MongoDB, and More](<https://devfeed.tech/articles/metasploit-wrap-up-langflow-mongodb-and-more-97858.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/pt-metasploit-wrap-up-langflow-mongodb-and-more>)

Author: Alan David Foster

Published: 2026-10-23T15:38:56Z

Content type: release

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [REST API](<https://devfeed.tech/topics/rest-api.md>), [Percona](<https://devfeed.tech/topics/percona.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [authentication-bypass](<https://devfeed.tech/tags/authentication-bypass.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [langflow](<https://devfeed.tech/tags/langflow.md>), [llm](<https://devfeed.tech/tags/llm.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [metasploit](<https://devfeed.tech/tags/metasploit.md>), [metasploit-weekly-wrapup](<https://devfeed.tech/tags/metasploit-weekly-wrapup.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [rce](<https://devfeed.tech/tags/rce.md>), [release](<https://devfeed.tech/tags/release.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

The release adds 11 Metasploit modules, with six covering Langflow vulnerabilities across versions 1.0.0-1.11.4: one authentication bypass, three unauthenticated RCEs, and two authenticated code execution flaws. Other additions include an unauthenticated OpenCTI RCE chain, three MongoDB auxiliary modules, an Apache Solr version scanner, and modules for 4gaBoards user information disclosure and authenticated Grafana command injection. The excerpt also notes Meterpreter improvements across Windows, Python, and PHP, plus fixes for HTTP fingerprinting crashes, redirect and FTP validation, resource leaks, and false-positive detections.

### Source excerpt

This release adds multiple new modules, and 6 of those modules point at a single target: Langflow, the open-source LLM workflow builder. Together they cover an authentication bypass (CVE-2026-93680), 3 unauthenticated remote code execution paths (CVE-2026-0768, CVE-2026-0769, and CVE-2026-10134), and 2 authenticated code execution flaws (CVE-2026-7873 and CVE-2026-93674), spanning Langflow releases from 1.0.0 through 1.11.4. Thanks to the work of rmhowe425, with research credit to Peter Girnus and n0k0. Beyond Langflow, open source contributor kmkz contributed a pre-auth RCE chain against OpenCTI. MongoDB coverage has also been expanded with 3 new auxiliary modules plus an Apache Solr version scanner thanks to the work of community member h00die. New Module Content (11)4gaBoards Mass User Information Disclosure (CVE-2026-53959) Authors: Balachandar Gowrisankar, de3erve (GitHub), and lucquach (GitHub) Type: Auxiliary Pull request: #21831 contributed by anirbala98 Path: gather/4gaboards_users_info_disclosure_cve_2026_53959 CVE reference: CVE-2026-53959 Description: Adds a module that exploits CVE-2026-53959, a broken access control vulnerability allowing mass user information disclosure in 4gaBoards versions 3.3.8 and below. The application's /api/users REST endpoint lets any authenticated user retrieve a full, unpaginated list of every user in the system. Missing authorization checks allow an attacker to retrieve the email, phone, organization, name, and SSO email addresses (ssoGoogleEmail, ssoGithubEmail, and others) of every user. Langflow AI Authentication Bypass (CVE-2026-93680) Author: Richard Howe Type: Auxiliary Pull request: #21942 contributed by rmhowe425 Path: gather/langflow_auth_bypass_cve_2026_93680 CVE reference: CVE-2026-93680 Description: Adds a new auxiliary module that leverages CVE-2026-93680, an authentication bypass vulnerability impacting Langflow versions 1.5.0 through 1.11.4. Apache Solr Version Scanner Author: h00die Type: Auxiliary Pull requ

## CVE-2026-109618 and CVE-2026-109619: Critical Unauthenticated Remote Code Execution in PHP

DevFeed: [CVE-2026-109618 and CVE-2026-109619: Critical Unauthenticated Remote Code Execution in PHP](<https://devfeed.tech/articles/cve-2026-109618-and-cve-2026-109619-critical-unauthenticated-remote-code-execution-in-php-92985.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/etr-cve-2026-109618-and-cve-2026-109619-critical-unauthenticated-remote-code-execution-in-php>)

Author: Rapid7

Published: 2026-10-21T15:22:52Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Error Handling](<https://devfeed.tech/topics/error-handling.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [emergent-threat-response](<https://devfeed.tech/tags/emergent-threat-response.md>), [emerging-threats](<https://devfeed.tech/tags/emerging-threats.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [php](<https://devfeed.tech/tags/php.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerabilities-and-exploits](<https://devfeed.tech/tags/vulnerabilities-and-exploits.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

PHP disclosed two critical vulnerabilities, both scored CVSSv4 9.2, that can enable unauthenticated RCE with web-worker privileges: CVE-2026-109618 corrupts memory during OOM cleanup, and CVE-2026-109619 uses stale state across requests. The excerpt reports confirmed exploit paths against mod_php and PHP-FPM, with mod_php considered highest risk; some paths depend on worker reuse, configuration, and application behavior. Rapid7 urges emergency updates: PHP 8.2.35, 8.3.36, 8.4.27, or 8.5.12, as applicable, or vendor packages containing both fixes. Older branches need vendor fixes, supplied backports, or an upgrade. Temporary administrative settings can reduce exposure to specific paths but do not fully remediate the flaws. The excerpt also recommends request-size and multipart controls; memory caps, container limits, and diagnostic suppression are not reliable substitutes for patching.

### Source excerpt

Overview On October 21, 2026, the PHP project announced security releases for two critical vulnerabilities in PHP. CVE-2026-109618 can corrupt memory during out-of-memory (OOM) handling, while CVE-2026-109619 is a use-after-free flaw involving state retained between requests. Both have a CVSSv4 score of 9.2 and both can allow for unauthenticated remote code execution (RCE) with the web worker's privileges. CVE CVSSv4 Description CVE-2026-109618 9.2 (Critical) RCE via OOM corruption CVE-2026-109619 9.2 (Critical) RCE via stale global state All installations serving web requests are at risk, including PHP-FPM, Apache mod_php, php-cgi, FrankenPHP, and LiteSpeed. The vendor considers mod_php the highest risk because exploitation can succeed before any application code runs. The advisories report that a successful RCE exploit was developed during research, including achieving RCE against Apache mod_php and PHP-FPM through different attack paths. As of October 21, 2026, there are multiple indications that this research is being independently reproduced, and a viable exploit is expected to be made public soon. Due to the extremely high deployment of PHP based web applications, exploitation in-the-wild is expected. Rapid7 recommends updating affected installations on an emergency basis, outside of normal patch cycles. Technical overviewCVE-2026-109618: Memory corruption during OOM handling According to the OOM advisory, PHP can abruptly abandon request processing when a memory allocation fails. If internal request data is only partly initialized, that exit can leave invalid data for request cleanup to use. Crafted multipart requests, used for forms and file uploads, can exhaust memory even when their size appears to meet PHP's configured limits. Application operations that allocate memory in response to attacker input can also trigger OOM. Apache mod_php runs cleanup even when request startup fails, enabling the demonstrated attack before application code executes. The advi

## Q3 2026 Threat Update: Attackers Are Exploiting Vulnerabilities Within 3 Days

DevFeed: [Q3 2026 Threat Update: Attackers Are Exploiting Vulnerabilities Within 3 Days](<https://devfeed.tech/articles/q3-2026-threat-update-attackers-are-exploiting-vulnerabilities-within-3-days-92871.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/tr-q3-2026-threat-update-attackers-exploiting-vulnerabilities-within-3-days>)

Author: Rapid7 Intelligence

Published: 2026-10-21T13:00:00Z

Content type: news

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [vulnerability management](<https://devfeed.tech/topics/vulnerability-management.md>), [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [ransomware](<https://devfeed.tech/topics/ransomware.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [also](<https://devfeed.tech/tags/also.md>), [apt](<https://devfeed.tech/tags/apt.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [data](<https://devfeed.tech/tags/data.md>), [days](<https://devfeed.tech/tags/days.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exploited-vulnerabilities](<https://devfeed.tech/tags/exploited-vulnerabilities.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [q3](<https://devfeed.tech/tags/q3.md>), [rapid7-intelligence](<https://devfeed.tech/tags/rapid7-intelligence.md>), [research](<https://devfeed.tech/tags/research.md>), [threat-research](<https://devfeed.tech/tags/threat-research.md>), [update](<https://devfeed.tech/tags/update.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

Rapid7 reports that newly exploited high- and critical-severity vulnerabilities were exploited an average of three days after public disclosure; 71% were exploited within seven days. Of 43 vulnerabilities tracked in Q3, 34 required no authentication or user interaction. The excerpt recommends identifying internet-facing assets, prioritizing known exploitation and unauthenticated access paths, and assessing compensating controls and detection coverage when immediate remediation is not possible. It also says 8% of tracked threat reporting cited AI as an operational component: in documented cases, human operators set targets and objectives while AI assisted with technique selection, target assessment, and adapting after failures. Underground monitoring found 41 posts advertising RDP or network access. These are excerpted findings, not a full account of the report.

### Source excerpt

Three days is the average time between a high-severity vulnerability becoming public and its exploitation, according to the latest Quarterly Threat Landscape Report from Rapid7. And 71% of the exploitation tracked in Q3 occurred within the first seven days. For security teams already managing growing vulnerability backlogs, this creates a difficult question: How do you reduce exposure when attackers can exploit vulnerabilities before your next patching window? Rapid7's Q3 2026 research brings together vulnerability intelligence, ransomware activity, APT tracking, and underground forum intelligence to show where attacker activity is concentrated. The exploitation window has narrowed, big time Rapid7 tracked 43 newly exploited high- and critical-severity vulnerabilities this quarter, down 7% from Q2 but still 19% higher than the same period last year. The number of newly exploited vulnerabilities isn't growing at the same rate as disclosures. The more pressing concern is how quickly attackers exploit the vulnerabilities they choose. On average, exploitation occurred just three days after public disclosure. The report also found that 80% of tracked exploitation occurred within 14 days and 90% within 30 days. That timeline creates a serious challenge for organizations relying on fixed remediation schedules. It also reinforces the need to distinguish between vulnerabilities that are theoretically severe and those that pose an immediate, exploitable risk. The report examines the exploitation timeline in greater detail, including the vulnerability characteristics that make certain exposures particularly attractive to attackers. Attackers are exploiting vulnerabilities that require no interaction Q3's vulnerability data reveals another concerning pattern: Of the 43 newly exploited high- and critical-severity vulnerabilities tracked, 34 (79%) required no authentication or user interaction. This provides attackers a potential path into exposed systems, no stolen credentials o

## Securing AI Agents with Controls Enforced Outside the Model

DevFeed: [Securing AI Agents with Controls Enforced Outside the Model](<https://devfeed.tech/articles/your-next-insider-threat-won-t-be-human-securing-ai-agents-from-the-outside-in-90263.md>)

Original publisher: [Read original article](<https://www.rapid7.com/blog/post/ai-inhuman-insider-threats-securing-agents>)

Author: Shriram Munde

Published: 2026-10-19T16:34:43Z

Content type: article

Language: en

Sources: [Rapid7 Cybersecurity](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Agentic SOC](<https://devfeed.tech/topics/agentic-soc.md>), [Security](<https://devfeed.tech/topics/security.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>)

Tags: [api-keys](<https://devfeed.tech/tags/api-keys.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [cybersecurity-company](<https://devfeed.tech/tags/cybersecurity-company.md>), [emerging-threats](<https://devfeed.tech/tags/emerging-threats.md>), [exposure-assessment-platform](<https://devfeed.tech/tags/exposure-assessment-platform.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [insider-threat](<https://devfeed.tech/tags/insider-threat.md>), [managed-detection-and-response](<https://devfeed.tech/tags/managed-detection-and-response.md>), [managed-security-solutions](<https://devfeed.tech/tags/managed-security-solutions.md>), [securing-ai](<https://devfeed.tech/tags/securing-ai.md>), [securing-ai-agents](<https://devfeed.tech/tags/securing-ai-agents.md>), [vulnerability-management](<https://devfeed.tech/tags/vulnerability-management.md>)

### AI overview

AI agents can use credentials and take consequential actions, while their behavior may vary across runs and can be manipulated through prompt injection. The article recommends enforcing controls outside the model through a policy layer that limits allowed actions and records decisions. Its security playbook covers agent identities, least privilege, tamper-evident logs, independent verification, red teaming, tested shutdown controls, incident sharing, memory risks, and SOC monitoring and response.

### Source excerpt

Why the controls on an AI agent have to live outside of it, and what a security operations team can implement and maintain those controls. The new privileged user in your environment Security teams spent two decades learning how to work with the people they trust most. Domain admins, DBAs, finance approvers and contractors with VPN access all get a mature playbook: verified identity, scoped access, logged activity and a fast way to revoke it all. Today, we're navigating the same kind of access with regard to AI agents. They read our mailboxes, query our data lakes, open tickets, push code and increasingly, act on production systems. Unlike a new hire, an agent can't be interviewed, background-checked or made to sign an acceptable-use policy. The industry has largely settled on one framing: AI agents are the new insider threat but that label only tells us half of the story. It tells us who to worry about, not where the controls should sit. Our argument is that the answer is a security idea from 1972, the reference monitor, and that the SOC is where it gets enforced in practice. Why agents break the trust model we had With traditional software, a security incident ends in a root cause. You find the vulnerable function, the misconfigured rule or the bad commit, and you fix it. The behavior lived in code we could read. Large language models don't give us that. We can't point to the training example or the set of weights that produced a specific decision. The same prompt can produce different actions on different runs. For a defender, that removes the most basic assumption we rely on: that the system will do tomorrow what it did today. The attack surface changes too, and computer science has an old name for this problem: the confused deputy. This is a trusted program tricked into misusing its own authority on someone else's behalf. An agent that reads a poisoned email, web page or document and then acts on hidden instructions is a confused deputy with API keys. No passwo

[Next page](<https://devfeed.tech/sources/rapid7-cybersecurity-blog.md?cursor=WyIyMDI2LTEwLTE5VDE2OjM0OjQzKzAwOjAwIiwgImQxM2JhNTQ0LTU1MzgtNDliOS04YjQ3LWU0YWM1MWEwNWRhZCJd>)