# CVE-2025-13833: Insecure TLS Fingerprint Validation in ForeScout SecureConnector Configuration Enables Remote Code Execution


- **Severity:** High 7.7 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-qjf6-95gx-vqgh

## What is CVE-2025-13833?

CVE-2025-13833 is a high-severity vulnerability in Forescout Technologies SecureConnector, published on 26 Oct 2026. 

### Official description

A vulnerability exists in SecureConnector for Windows when the “Additional Appliance Connections” setting is enabled and the agent’s configuration file contains more than three trusted‑server entries. Some entries omit TLS certificate fingerprints, which allows the agent to accept and establish sessions with a malicious server. An attacker who controls the wired or wireless network can redirect traffic to a malicious server. The attacker can then use the agent’s built‑in command/file features to execute arbitrary commands as SYSTEM, granting full administrative control and the ability to disable endpoint protections or exfiltrate data.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2025-13833?


## How do I fix CVE-2025-13833?

No fix has been published for CVE-2025-13833 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-13833 being exploited?

There is no known exploitation of CVE-2025-13833 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13833 and fix it if it is affected.

What it is: CVE-2025-13833 is a high-severity vulnerability in Forescout Technologies SecureConnector, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2025-13833 in the wild and no public exploit code.

Affected product: Forescout Technologies SecureConnector. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-13833/ (Markdown: https://insights.sbomify.com/CVE-2025-13833/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13833
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13833
- OSV: https://osv.dev/vulnerability/CVE-2025-13833

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13833/
Summaries are generated and may contain mistakes; the official description above is the record.