# CVE-2025-22937: Privilege escalation in n/a

> Attackers can escalate privileges on Adtran 411 ONT devices via unspecified vectors, potentially gaining unauthorized control.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 31 Mar 2025
- **Updated:** 18 Aug 2025
- **Also known as:** GHSA-hmpw-vvvc-x4mh

## What is CVE-2025-22937?

CVE-2025-22937 is a critical vulnerability in n/a, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Adtran 411 ONT vL80.00.0011.M2 allows attackers to escalate privileges via unspecified vectors.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Adtran 411 Firmware.

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

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

## Is CVE-2025-22937 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-22938](https://insights.sbomify.com/CVE-2025-22938/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-22939](https://insights.sbomify.com/CVE-2025-22939/): Command injection in n/a (critical 9.8)
- [CVE-2025-22941](https://insights.sbomify.com/CVE-2025-22941/): Command injection in n/a (critical 9.8)
- [CVE-2025-22940](https://insights.sbomify.com/CVE-2025-22940/): Auth bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22937 is a critical vulnerability in n/a, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22937 exists.

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-22937/ (Markdown: https://insights.sbomify.com/CVE-2025-22937/index.md)
```

## Sources

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

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