# CVE-2026-73542: Weak cryptography in Multiple SEIKO EPSON printers and scanners

> Attackers can intercept communication data from Epson printers and scanners via man-in-the-middle attacks due to revoked root certificates.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-mw8v-5vg6-vwx7

## What is CVE-2026-73542?

CVE-2026-73542 is a medium-severity vulnerability in Multiple SEIKO EPSON printers and scanners, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SEIKO EPSON printers and scanners contain revoked root certificates. A man-in-the-middle attack may allow an attacker to obtain communication data transmitted by the product. As for the details of the affected products and versions, refer to the vendor's information.

Weakness: CWE-296 (Improper Following of a Certificate's Chain of Trust)

## Which versions are affected by CVE-2026-73542?


## How do I fix CVE-2026-73542?

No fix has been published for CVE-2026-73542 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73542 being exploited?

There is no known exploitation of CVE-2026-73542 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73542 and fix it if it is affected.

What it is: CVE-2026-73542 is a medium-severity vulnerability in Multiple SEIKO EPSON printers and scanners, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73542 in the wild and no public exploit code.

Affected product: Multiple SEIKO EPSON printers and scanners. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73542/ (Markdown: https://insights.sbomify.com/CVE-2026-73542/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73542
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73542
- OSV: https://osv.dev/vulnerability/CVE-2026-73542

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73542/
Summaries are generated and may contain mistakes; the official description above is the record.