# CVE-2025-23262: Missing authorization in ConnectX GA

> Local attackers can bypass authorization in the management interface to modify configuration, causing denial of service, privilege escalation, and data tampering.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2025
- **Updated:** 4 Sep 2025
- **Also known as:** GHSA-cq7v-6gr4-8hx4

## What is CVE-2025-23262?

CVE-2025-23262 is a medium-severity missing authorization vulnerability in NVIDIA ConnectX GA, published on 4 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA ConnectX contains a vulnerability in the management interface, where an attacker with local access could cause incorrect authorization to modify the configuration. A successful exploit of this vulnerability might lead to denial of service, escalation of privileges, information disclosure, and data tampering.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-23262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23262 is a medium-severity missing authorization vulnerability in NVIDIA ConnectX GA, published on 4 Sep 2025. 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-2025-23262 in the wild and no public exploit code.

Affected product: NVIDIA ConnectX GA. 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-23262/ (Markdown: https://insights.sbomify.com/CVE-2025-23262/index.md)
```

## Sources

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

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