# CVE-2021-43718: Auth bypass in n/a

> Remote attackers can bypass authentication to cause a denial of service on Epson projectors via crafted HTTP requests.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-7m7m-mm9g-q3cc

## What is CVE-2021-43718?

CVE-2021-43718 is a medium-severity authentication bypass vulnerability in n/a, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Authentication Bypass vulnerability exists in EPSON EH-TW5350 EPSON 150075647YWWV110, which could let a remote malicious user cause a Denial of Service via specially crafted series of HTTP..

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2021-43718?


## How do I fix CVE-2021-43718?

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

## Is CVE-2021-43718 being exploited?

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

Public exploit code:

- Published Epson EH-TW5350 CVE · Web Control authentication bypass · B-BEAM-BOB team (github_poc): https://github.com/dpfkdlemtp/CVE-2021-43718

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43718 and fix it if it is affected.

What it is: CVE-2021-43718 is a medium-severity authentication bypass vulnerability in n/a, published on 18 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-2021-43718 in the wild and no public exploit code.

Affected product: n/a. 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-2021-43718/ (Markdown: https://insights.sbomify.com/CVE-2021-43718/index.md)
```

## Sources

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

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