CVE-2026-36612 Security feature bypass in n/a
Medium 6.4
Published
Updated
Check this codebase for CVE-2026-36612 and fix it if it is affected.
What it is: CVE-2026-36612 is a medium-severity vulnerability in n/a, published on 3 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-36612 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-36612/ (Markdown: https://insights.sbomify.com/CVE-2026-36612/index.md)
Weak WPS lockout policy allows attackers to brute-force PINs and gain unauthorized access to the router.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-36612?
CVE-2026-36612 is a medium-severity vulnerability in n/a, published on 3 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
Mercusys AC12G (EU) V1 with firmware AC12G(EU)_V1_200909 enables WPS 2.0 by default with a weak lockout policy (60-second lockout after 10 attempts).
Which versions are affected by CVE-2026-36612?
How do I fix CVE-2026-36612?
No fix has been published for CVE-2026-36612 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-36612 being exploited?
There is no known exploitation of CVE-2026-36612 in the wild and no public exploit code.
Sources
Also known as GHSA-m39f-rg22-q2x7.