CVE-2026-20206
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 · uneditedA vulnerability in the BrowserBot component of Cisco ThousandEyes Enterprise Agent could have allowed an authenticated, remote attacker to execute arbitrary commands on Agents on behalf of the BrowserBot synthetics orchestration process. Cisco has addressed this vulnerability in the Cisco ThousandEyes Enterprise Agent, and no customer action is needed. This vulnerability was due to insufficient input validation of command arguments that are supplied by the user. Prior to this vulnerability being addressed, an attacker could have exploited this vulnerability by authenticating to the ThousandEyes SaaS and submitting crafted input into the affected parameter. A successful exploit could have allowed the attacker to execute arbitrary commands within the BrowserBot container as the node user. To exploit this vulnerability, the attacker must have valid user credentials for the ThousandEyes SaaS and the ability to manage transaction tests.
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 · high confidenceThis vulnerability in Cisco ThousandEyes Enterprise Agent's BrowserBot component allowed authenticated attackers with transaction test management privileges to execute arbitrary commands within the BrowserBot container as the node user. The root cause was insufficient input validation on command arguments supplied by users, enabling command injection via crafted input to affected parameters.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify ThousandEyes Enterprise Agent is installedCheck for running processes: ps aux | grep -i 'thousandeyes\|te-agent' or look for installation directories such as /opt/thousandeyes or /var/lib/thousandeyesAffected if The ThousandEyes Enterprise Agent software is present on the system
-
Determine the installed agent versionRun 'te-agent --version' or check /opt/thousandeyes/agent/version.txt if the agent is installed locally; alternatively check the version reported in the ThousandEyes dashboard under Agent settingsAffected if The version cannot be determined or is older than the patched release
-
Confirm BrowserBot transaction test capability is accessibleLog into the ThousandEyes SaaS dashboard and verify if the account has access to create or manage Transaction Tests (look for Transaction > Transaction Tests menu); or check if the agent has transaction test capabilities enabled in its configurationAffected if Transaction test functionality is available and the user has manage transaction tests permissions
-
Inspect for signs of exploitationReview BrowserBot container logs for unusual command patterns: docker logs [container_name] 2>&1 | grep -E 'command|exec|bash|sh' or check /var/log/te-agent.log for suspicious entries; also review for unexpected outbound network connections from the agentAffected if Unexplained command execution patterns or unauthorized connections are found in logs or network traffic
If ThousandEyes Enterprise Agent is running with an unpatched version and the account has manage transaction tests permissions with BrowserBot transaction test features accessible, the environment is vulnerable to command injection.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataNo customer action required as Cisco has already addressed this vulnerability in the ThousandEyes Enterprise Agent. Organizations should verify their agents are updated to the patched version.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20206 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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