Thousandeyes Endpoint AgentApplication · Cisco

CVE-2025-20259

MEDIUM · 5.3 CVSS v3.1 Published 2025-06-04
Fix available
A fix is available. Upgrade to 2.3.3 or later.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple vulnerabilities in the update process of Cisco ThousandEyes Endpoint Agent for Windows could allow an authenticated, local attacker to delete arbitrary files on an affected device. These vulnerabilities are due to improper access controls on files that are in the local file system. An attacker could exploit these vulnerabilities by using a symbolic link to perform an agent upgrade that redirects the delete operation of any protected file. A successful exploit could allow the attacker to delete arbitrary files from the file system of the affected device.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability exists in Cisco ThousandEyes Endpoint Agent for Windows update process where improper access controls on files allow an authenticated local attacker to delete arbitrary files by using symbolic link manipulation during agent upgrades.

MitigationApply vendor patches when available; limit local system access to trusted authenticated users; monitor upgrade processes for suspicious symlink activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Thousandeyes Endpoint AgentApplication
Affected:< 2.3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cisco ThousandEyes Endpoint Agent is installed
    Check for the presence of the agent on the Windows system through installed programs list, running services, or installed directories
    Affected if The agent is not found on the system, the vulnerability does not apply
  2. Identify the installed version
    Use system tools or the agent's own interface to determine the exact version number of the installed Cisco ThousandEyes Endpoint Agent
    Affected if The version is 2.3.3 or higher, the system is not affected; if the version is below 2.3.3 or cannot be determined, the system may be affected
  3. Confirm the upgrade/update component exists
    Verify that the agent's upgrade functionality is present on the system (the vulnerability occurs during agent upgrades)
    Affected if The upgrade component is missing or disabled, exploitation may not be possible
  4. Check for symlink manipulation during recent upgrades
    Review upgrade logs or monitor for any symbolic link files created in agent upgrade directories that point to unexpected locations
    Affected if Suspicious symlinks or unauthorized file deletions occurred during recent upgrade processes, the vulnerability may have been exploited

The system is affected if Cisco ThousandEyes Endpoint Agent is installed with a version lower than 2.3.3 and the upgrade functionality is present and accessible to authenticated local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.3 or later
Fixed in 2.3.3
Interim mitigation

Apply vendor patches when available; limit local system access to trusted authenticated users; monitor upgrade processes for suspicious symlink activity.

Recommended fix High confidence

2.3.3

  1. 1. Verify current ThousandEyes Endpoint Agent version by checking the agent UI or system information
  2. 2. Download the ThousandEyes Endpoint Agent version 2.3.3 or later from the official Cisco ThousandEyes portal
  3. 3. Ensure you have appropriate authentication credentials for the agent upgrade process
  4. 4. Initiate the agent upgrade through the ThousandEyes management console or by running the installer with appropriate local authentication
  5. 5. Confirm the upgrade completes successfully and verify the new version is 2.3.3 or later
  6. 6. Test that the endpoint agent is functioning normally post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Thousandeyes Endpoint Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20259 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data