ESC/POS: Missing Authentication for Critical Functionality
CVE-2026-23767 is a critical-severity missing authentication for critical functionality vulnerability in ESC/POS from Seiko Epson, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected ESC/POS versions: All products implementing ESC/POS. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of ESC/POS you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on epson.jp for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Seiko Epson | ESC/POS | All products implementing ESC/POS | Not stated |
| Epson | Sb-h50 Firmware | Not specified in the record | Not stated |
| Epson | Tm-h6000v Firmware | Not specified in the record | Not stated |
| Epson | Tm-l100 Firmware | Not specified in the record | Not stated |
| Epson | Tm-m10 Firmware | Not specified in the record | Not stated |
| Epson | Tm-m30 Firmware | Not specified in the record | Not stated |
| Epson | Tm-m30ii Firmware | Not specified in the record | Not stated |
| Epson | Tm-m30ii-h Firmware | Not specified in the record | Not stated |
| Epson | Tm-m30ii-s Firmware | Not specified in the record | Not stated |
| Epson | Tm-m30ii-sl Firmware | Not specified in the record | Not stated |
| Epson | Tm-m30iii Firmware | Not specified in the record | Not stated |
| Epson | Tm-m30iii-h Firmware | Not specified in the record | Not stated |
| Epson | Tm-m55 Firmware | Not specified in the record | Not stated |
| Epson | Tm-p20ii Firmware | Not specified in the record | Not stated |
| Epson | Tm-p80ii Firmware | Not specified in the record | Not stated |
| Epson | Tm-p20 Firmware | Not specified in the record | Not stated |
| Epson | Tm-p60ii Firmware | Not specified in the record | Not stated |
| Epson | Tm-p80 Firmware | Not specified in the record | Not stated |
| Epson | Tm-t20ii Firmware | Not specified in the record | Not stated |
| Epson | Tm-t20iii Firmware | Not specified in the record | Not stated |
| Epson | Tm-t88vi Firmware | Not specified in the record | Not stated |
| Epson | Tm-t88vi-ihub Firmware | Not specified in the record | Not stated |
| Epson | Tm-t88vii Firmware | Not specified in the record | Not stated |
| Epson | Ub-r04 Firmware | Not specified in the record | Not stated |
| Epson | Ub-e04 Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- jvn.jp/en/ta/JVNTA97995322/Third Party Advisory
Other references
Recent Missing Authentication for Critical Functionality vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 7.7 High severity
- 8.2 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.