CVE-2026-3356: Anritsu Remote Spectrum Monitor MS27100A · Missing Authentication
Affects Anritsu Remote Spectrum Monitor MS27100ASource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 31 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AnritsuRemote Spectrum Monitor MS27100A | Affected
| Fixed in– |
| AnritsuRemote Spectrum Monitor MS27101A | Affected
| Fixed in– |
| AnritsuRemote Spectrum Monitor MS27102A | Affected
| Fixed in– |
| AnritsuRemote Spectrum Monitor MS27103A | Affected
| Fixed in– |
AI-suggested
No patches or official fixes are currently available for this vulnerability. Since the issue is inherent to the device design and affects all versions, users should consider isolating the device from untrusted networks and restricting access to trusted personnel only. Monitor vendor communications for any future advisories or firmware updates addressing this issue.
Description
The MS27102A Remote Spectrum Monitor is vulnerable to an authentication bypass that allows unauthorized users to access and manipulate its management interface. Because the device provides no mechanism to enable or configure authentication, the issue is inherent to its design rather than a deployment error.