# CVE-2025-67822: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication in Mitel MiVoice MX-ONE to gain unauthorized access to user or admin accounts.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2026
- **Updated:** 16 Jan 2026
- **Also known as:** GHSA-86mm-wwrr-f4h4

## What is CVE-2025-67822?

CVE-2025-67822 is a critical authentication bypass vulnerability in n/a, published on 15 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Provisioning Manager component of Mitel MiVoice MX-ONE 7.3 (7.3.0.0.50) through 7.8 SP1 (7.8.1.0.14) could allow an unauthenticated attacker to conduct an authentication bypass attack due to improper authentication mechanisms. A successful exploit could allow an attacker to gain unauthorized access to user or admin accounts in the system.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Mitel Mivoice Mx-One.

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

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

## Is CVE-2025-67822 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-36446](https://insights.sbomify.com/CVE-2024-36446/): Auth bypass in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67822 is a critical authentication bypass vulnerability in n/a, published on 15 Jan 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-2025-67822 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-2025-67822/ (Markdown: https://insights.sbomify.com/CVE-2025-67822/index.md)
```

## Sources

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

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