# CVE-2025-33207: Missing authorization in BlueField GA

> A user with VF access can cause denial of service by sending malicious commands to the firmware due to improper access control.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-xvmw-v642-vxxr

## What is CVE-2025-33207?

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

### Official description

NVIDIA ConnectX and Bluefield contain a vulnerability in a control register, where a user with VF access could cause improper access control for the register interface by sending a malicious command to the firmware. A successful exploit of this vulnerability might lead to denial of service.

Weakness: CWE-1262 (Improper Access Control for Register Interface)

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


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

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

## Is CVE-2025-33207 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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