Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-4660: A remote code execution vulnerability exists in the Windows agent component of SecureConnector due to improper

56
This month
CRITICAL 9.8REMOTEUPGRADE

CVE-2025-4660 is a critical-severity flaw (CVSS 9.8) affecting secureconnector. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A remote code execution vulnerability exists in the Windows agent component of SecureConnector due to improper access controls on a named pipe. The pipe is accessible to the Everyone group and does not restrict remote connections, allowing any network-based attacker to connect without authentication. By interacting with this pipe, an attacker can redirect the agent to communicate with a rogue server that can issue commands via the SecureConnector

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.2% (top 32%)
CISA exploited listNo
WeaknessCWE-276
Published2025-05-13
Last modified2026-06-17
Publisher (CNA): Forescout · Vendor: forescout

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

forescout secureconnector UPGRADE
Affected: >= 11.1.02.1019 and < 11.3.7
Fixed in: 11.3.7
Safe to downgrade to: a release before 11.1.02.1019
1. Check installed version
apt-cache policy secureconnector || rpm -q secureconnector || secureconnector --version
2. UPGRADE to 11.3.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade secureconnector
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade secureconnector
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 11.1.02.1019 (Debian / Ubuntu)
apt-cache madison secureconnector sudo apt install secureconnector=<VERSION_BEFORE_11.1.02.1019> sudo apt-mark hold secureconnector
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list secureconnector sudo dnf downgrade secureconnector-<VERSION_BEFORE_11.1.02.1019> sudo dnf versionlock add secureconnector
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-4660?

secureconnector: upgrade to 11.3.7. Exact commands for each OS are on this page.

Is CVE-2025-4660 being exploited?

CVE-2025-4660 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-4660 affect?

CVE-2025-4660 affects secureconnector. Severity is critical (CVSS 9.8). A remote code execution vulnerability exists in the Windows agent component of SecureConnector due to improper access controls on a named pipe. The pipe is accessible to the Everyone group and does not restrict remote connections, allowing

How urgent is CVE-2025-4660?

Priority 56/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Windows vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.