# CVE-2026-36605: Denial of service in n/a

> An attacker can cause a persistent crash in Mercusys AC12G routers by sending crafted incomplete HTTP requests, requiring physical power cycling to recover.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jun 2026
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-j2fc-v5xj-h5gr

## What is CVE-2026-36605?

CVE-2026-36605 is a medium-severity denial of service vulnerability in n/a, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mercusys AC12G (EU) V1 router with firmware AC12G(EU)_V1_200909 is vulnerable to a HTTP denial of service via a low number of crafted incomplete HTTP requests, causing a persistent crash that requires physical power cycling to recover.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-36605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36605 is a medium-severity denial of service vulnerability in n/a, published on 3 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-36605 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-2026-36605/ (Markdown: https://insights.sbomify.com/CVE-2026-36605/index.md)
```

## Sources

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

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