Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain access to instrument control network
-
DeliveryReach SCPI remote-control interface
-
ExploitSend crafted FILESystem:MOUNT:DRIve command
-
ExecutionInject unneutralized shell metacharacters
-
PersistExecute OS commands with elevated privileges
-
ImpactFull compromise of instrument
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to the instrument's SCPI remote-control interface (LAN/VXI-11/raw-socket control port) and the ability to issue the FILESystem:MOUNT:DRIve SCPI command; the attacker must be able to send command input that reaches this specific handler. The affected feature is the drive-mount filesystem SCPI command, present on Tektronix 3 Series MDO devices running firmware before 1.21.1 - devices patched to 1.21.1 or later are not affected. Limiting factors: CVSS indicates PR:L, so some level of existing access/privilege to the control interface is assumed (authentication requirement not independently confirmed from available data), and the instrument must be network-exposed rather than operated purely via its front panel; no user interaction (UI:N) is required. Realistic risk is bounded to attackers who already have a foothold on the lab/engineering network where the scope is deployed. |
| Impact | This is a credible operational-technology risk, though not a mass-exploitation emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity attack requiring some level of existing privilege (PR:L), with full High impact to confidentiality, integrity, and availability, yielding the 8.8 base score. The flaw is an OS command injection (CWE-78) in the FILESystem:MOUNT:DRIve SCPI command handler that executes with elevated privileges, so a successful attack likely yields root/administrative control of the instrument's embedded OS - an unusually high technical impact for lab/test equipment. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the real-world threat is therefore driven by impact severity rather than demonstrated exploitation. The PR:L metric is the key limiting signal: exploitation presumes an attacker can reach and interact with the SCPI control interface (typically exposed over LAN/VXI-11/raw socket on a lab or engineering network), which constrains this to attackers already on the network segment rather than internet-wide opportunistic actors. Note a potential conflict to verify with the vendor: SCPI control interfaces on many instruments are unauthenticated by design, which would argue for PR:N - NVD rates it PR:L, so the precise authentication prerequisite should be confirmed against the Tektronix advisory (TEK-PSA-002-092026). |
| Exploit ScenarioDerived | An attacker with access to the lab/engineering network segment where a Tektronix 3 Series MDO is reachable sends a crafted FILESystem:MOUNT:DRIve SCPI command containing shell metacharacters to the instrument's remote control interface. Because user input is insufficiently neutralized, the injected commands execute with elevated privileges on the device's embedded OS, giving the attacker full control of the instrument. No public exploit code was identified at time of analysis, and the CVSS low attack complexity (AC:L) indicates no special timing or race conditions are needed once interface access is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 17, 2026
OS command injection in the FILESystem:MOUNT:DRIve SCPI command handler of Tektronix 3 Series MDO oscilloscopes running firmware before 1.21.1 allows authenticated, low-privileged attackers who can reach the instrument's remote-control interface to execute arbitrary operating system commands with elevated privileges (CVSS 8.8, CWE-78, PR:L/UI:N). Any 3 Series MDO that exposes its SCPI control interface (LAN/VXI-11 or raw socket) to a lab or engineering network is in scope, and the attack requires no user interaction. No public exploit code and no CISA KEV listing were identified at time of analysis, and no EPSS score was supplied in the available data, so the realistic risk is concentrated on network-exposed instruments rather than mass exploitation.
RemediationAI
Vendor-released patch: firmware version 1.21.1 - upgrade every 3 Series MDO instrument currently below that build, following the Tektronix advisory TEK-PSA-002-092026 (https://download.tek.com/document/TEK-PSA-002-092026.pdf) and the product page at https://www.tek.com/en/products/oscilloscopes/3-series-mdo for the download and update procedure; because the flaw sits in a network-facing SCPI handler, patching is the only complete fix and should be prioritized for any instrument reachable from shared lab or engineering subnets. Where immediate upgrade is not possible, apply compensating controls that reduce reachability of the SCPI service: firewall or ACL-restrict the instrument's VXI-11 and raw-socket control ports to a small allowlist of test-automation hosts (trade-off: breaks legitimate remote automation from non-listed systems, so inventory automation clients first), and place instruments on an isolated instrument VLAN segmented from user workstations and the internet (trade-off: added routing/NAT complexity for test benches that pull data centrally). For instruments that do not require programmatic control, disable the LAN/remote interface and operate from the front panel only (trade-off: loses all remote automation and centralized logging of measurements). Because the CVSS vector is PR:L, treat access to the control interface as a privilege boundary: replace any default or shared credentials, restrict who on the lab network can open sessions to the instrument, and log or monitor SCPI traffic for FILESystem:MOUNT:DRIve invocations as a detection signal (trade-off: SCPI sessions are typically unencrypted, so monitoring provides limited visibility and may itself expose command contents). No vendor workaround short of the 1.21.1 firmware is documented in the available references, and no public exploit code was identified at time of analysis.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the SCPI (Standard Commands for Programmable Instruments) remote-control service on Tektronix 3 Series MDO mixed-domain oscilloscopes, tracked as CPE cpe:2.3:a:tektronix:3_series_mdo. SCPI is the ASCII command protocol instruments expose over LAN transports such as VXI-11 and raw TCP sockets, and it is normally used by test-automation frameworks to configure measurements and manipulate the instrument's filesystem. The FILESystem:MOUNT:DRIve subcommand is intended to mount a drive, but the handler passes user-supplied arguments into an operating-system shell call without sufficient neutralization, which is the classic CWE-78 OS command injection root cause: untrusted input crosses from a parsed command string into a privileged shell context, so shell metacharacters embedded in a mount argument are interpreted as commands. Because the handler runs in an elevated context on the instrument's embedded OS, successful injection yields high confidentiality, integrity, and availability impact (CVSS 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) - but the PR:L metric means the attacker must already hold some level of access/privilege to the control interface, and the instrument must be reachable over the network rather than operated only from the front panel. Authentication requirements for that interface are not independently confirmed from the available data.
Know when 3 Series Mdo gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable SCPI handler (AV:N) with no special complexity (AC:L); PR:L reflects assumed control-interface access, and command execution at elevated privilege gives full C:H/I:H/A:H.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
An issue was discovered on Tektronix 3 Series MDO devices before 1.21.1. An OS command injection vulnerability exists in the FILESystem:MOUNT:DRIve SCPI command handler. Insufficient neutralization of user-supplied input allows remote attackers to execute arbitrary operating system commands with elevated privileges.
Executive ViewAI
Tektronix 3 Series MDO oscilloscopes running firmware before 1.21.1 contain an authenticated command-injection flaw in the remote SCPI control interface that could allow a low-privileged user with network reachability to execute operating-system commands at elevated privileges on lab instruments. Because these oscilloscopes typically reside on engineering and lab networks, leadership should treat any exposed unit as a potential foothold into test environments and prioritize inventory, network restriction, and firmware remediation for dependent teams. No public exploit code or CISA KEV listing was identified at time of analysis, so near-term risk is concentrated on instruments whose SCPI interfaces are reachable from untrusted network segments rather than on mass exploitation.
No vendor-released patch identified at time of analysis. Interim mitigations include restricting SCPI remote-control access (LAN/VXI-11 and raw socket) to approved engineering hosts through firewall ACLs or a dedicated instrument VLAN, disabling the remote-control interface on instruments that do not require it, enforcing strong unique credentials and least-privilege accounts, monitoring instrument authentication and connection logs for anomalous SCPI commands, and segmenting oscilloscopes from general-purpose lab and corporate networks to limit lateral movement if an authenticated attacker reaches the interface.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
EUVD-2026-103206
GHSA-r8hj-gr47-x24w
NVD
CVE.org
VulDB
Exploit-DB