CVE-2025-11155: SATO S86-ex 203dpi · Weak Encoding for Password
Affects SATO S86-ex 203dpiSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SATO S86-ex 203dpi | Affected
| Fixed in– |
AI-suggested
First, isolate SATO printers on dedicated VLANs or network segments with strict access controls to limit exposure to trusted users and systems only. Employ network monitoring and intrusion detection systems to detect unusual access patterns to printer web interfaces. Where possible, enforce the use of VPNs or encrypted tunnels (e.g., IPsec) for accessing printer management interfaces to prevent interception of HTTP traffic. Disable or restrict web interface access if not required, or configure access control lists to limit management access to specific IP addresses. Educate users about the risks of connecting to unsecured networks where printers are accessible. Regularly audit network configurations and printer settings to detect unauthorized changes. Engage with the vendor for updates or firmware patches and plan for timely deployment once available. Consider replacing affected devices with models supporting secure authentication and encrypted management protocols if risk tolerance is low.
Description
The credentials required to access the device's web server are sent in base64 within the HTTP headers. Since base64 is not considered a strong cipher, an attacker could intercept the web request handling the login and obtain the credentials.