# CVE-2025-62772: Security feature bypass in M6a

> Attackers can hijack user sessions on Mercku M6a routers because session tokens remain valid for months, allowing unauthorized access.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-h5x7-xvx7-3c6r

## What is CVE-2025-62772?

CVE-2025-62772 is a low-severity vulnerability in Mercku M6a, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On Mercku M6a devices through 2.1.0, session tokens remain valid for at least months in some cases.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2025-62772?


## How do I fix CVE-2025-62772?

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

## Is CVE-2025-62772 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62772 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62772 and fix it if it is affected.

What it is: CVE-2025-62772 is a low-severity vulnerability in Mercku M6a, published on 22 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62772 exists.

Affected product: Mercku M6a. 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-2025-62772/ (Markdown: https://insights.sbomify.com/CVE-2025-62772/index.md)
```

## Sources

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

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