HighPublic exploit

Remote Code Execution in Windows SecureConnector Agent Named Pipe

IdentifiersCVE-2025-4660CWE-284

CVE-2025-4660 is a remote code execution vulnerability affecting the Windows agent component of SecureConnector. The issue is caused by improper access controls on a named pipe exposed by the agent. The pipe is accessible to the Everyone group and does not restrict remote connections, which allows unauthenticated network-based attackers to connect to it. By interacting with the named pipe, an attacker can redirect the agent to communicate with an attacker-controlled rogue server, which can then issue commands through the SecureConnector Agent. The vulnerability is described as affecting Windows only and does not impact Linux or macOS Secure Connector deployments.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an unauthenticated remote attacker on the network to cause the Windows SecureConnector Agent to connect to an attacker-controlled server and accept commands through that channel. This can result in remote code execution in the context of the affected agent, enabling compromise of the host running the Windows agent and potentially follow-on actions such as persistence, lateral movement, or execution of arbitrary attacker-supplied commands.

Mitigation

If you can’t patch tonight, do this now.

Until patches can be applied, limit network access to systems running the Windows SecureConnector Agent, especially from untrusted or broadly reachable network segments. Restrict or firewall SMB/RPC and other mechanisms that permit remote named pipe access where operationally feasible. Use host-based controls to prevent unauthorized remote connections to the agent, and monitor for unexpected agent connections to untrusted or unknown servers. If possible, disable the affected Windows agent service temporarily in high-risk environments until remediation is completed. Linux and macOS Secure Connector deployments are not affected.

Remediation

Patch, then assume compromise.

Apply the vendor-provided fix or update for CVE-2025-4660 in the Windows SecureConnector Agent. The remediation should ensure the named pipe permissions are restricted so that it is not accessible to the Everyone group and that remote connections are properly limited or disallowed unless explicitly required and securely authenticated. If a patched version is available from the vendor, upgrade affected Windows SecureConnector Agent installations to that version.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app

CVE-2025-4660MaturityPoCVerified exploit

This repository provides a proof-of-concept (PoC) exploit for CVE-2025-4660, a remote code execution vulnerability in Forescout SecureConnector for Windows. The repository contains two main Python scripts: 1. forescout_redirect.py: This is the exploit script that connects to the SecureConnector agent's named pipe (\\<target_host>\pipe\_FS_SC_UNINSTALL_PIPE) and sends a specially crafted packet to redirect the agent to an attacker-controlled IP and port. This enables the attacker to hijack the agent's communication channel. 2. forescout_c2.py: This script implements a simple command-and-control (C2) server that speaks the SecureConnector protocol. Once an agent is redirected, the C2 server can interact with it, issuing commands such as directory listing, process listing, file retrieval, and arbitrary shell command execution via a custom XML-based protocol. The exploit requires the attacker to have network access to the target system and the ability to connect to the named pipe. The C2 server provides an interactive shell for managing compromised agents. The repository is structured as a PoC and does not include weaponized or automated exploitation features.

NetSPIDisclosed Jul 3, 2025pythonnetworklocal

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

ForescoutSecureconnectorapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

12 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

12 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity12