Sb H50 FirmwareOperating system · Epson

CVE-2026-23767

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
ESC/POS, a printer control language designed by Seiko Epson Corporation, lacks mechanisms for user authentication and command authorization, does not provide controls to restrict sources or destinations of network communication, and transmits commands without encryption or integrity protection.

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 confidence

ESC/POS printer command language lacks fundamental security mechanisms including user authentication, command authorization, network communication controls, and encryption/integrity protection. This allows any network-adjacent attacker to send arbitrary printer commands, intercept traffic, or modify commands in transit.

MitigationDeploy network segmentation (VLANs) to isolate printers, implement strict firewall rules limiting printer access to authorized systems, and consider VPN tunneling or dedicated network paths for print traffic to compensate for the protocol's inherent lack of security.

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
Sb H50 FirmwareOperating system
Affected:all versions
Tm H6000v FirmwareOperating system
Affected:all versions
Tm L100 FirmwareOperating system
Affected:all versions
Tm M10 FirmwareOperating system
Affected:all versions
Tm M30 FirmwareOperating system
Affected:all versions
Tm M30ii FirmwareOperating system
Affected:all versions
Tm M30ii H FirmwareOperating system
Affected:all versions
Tm M30ii S FirmwareOperating system
Affected:all versions

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify network-connected Epson printers
    Scan your network for devices with manufacturer OUI matching Epson (typically 00:26:AB or similar) and service ports 9100, 80, or 443 open, or manually inspect printer inventory records for models: Sb H50, Tm H6000v, Tm L100, Tm M10, Tm M30, Tm M30ii, Tm M30ii H, Tm M30ii S
    Affected if Any of the listed Epson printer models are present on your network
  2. Verify printer network accessibility
    Check if the printer IP address is reachable from network segments that contain untrusted or guest devices, or test with a port scan from an untrusted network segment
    Affected if The printer is reachable from network segments beyond the trusted print server or administrative VLAN
  3. Check network segmentation status
    Review VLAN configuration or firewall rules to determine if the printer is isolated in a dedicated VLAN or has access control lists restricting communication to only authorized print server IPs
    Affected if No VLAN isolation or firewall rules restrict printer access to specific authorized systems
  4. Confirm no VPN or encrypted tunnel is in use
    Verify that print traffic is not encapsulated within a VPN tunnel or other encrypted channel by inspecting network paths between print clients and the printer
    Affected if Print traffic traverses the network in plain text without encryption or tunnel protection

You are affected if any of the listed Epson printer models are network-accessible from segments outside your trusted print infrastructure without VLAN isolation, firewall rules, or VPN tunneling protecting the communication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Deploy network segmentation (VLANs) to isolate printers, implement strict firewall rules limiting printer access to authorized systems, and consider VPN tunneling or dedicated network paths for print traffic to compensate for the protocol's inherent lack of security.

Fix this in Sb H50 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23767 — 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-2026-23767 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