# CVE-2025-33216: Integer overflow in SNAP-4 Container

> An attacker on a VM can cause a denial of service in the storage service by sending crafted configurations that trigger an incorrect buffer size calculation.

- **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:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-j44v-7j32-mr9x

## What is CVE-2025-33216?

CVE-2025-33216 is a medium-severity vulnerability in NVIDIA SNAP-4 Container, published on 24 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA SNAP-4 Container contains a vulnerability in the configuration interface where an attacker on a VM may cause an incorrect calculation of buffer size by sending crafted configurations. A successful exploit of this vulnerability may lead to crash of the SNAP service, causing denial of service of the storage service to the host.

Weakness: CWE-131 (Incorrect Calculation of Buffer Size)

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


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

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

## Is CVE-2025-33216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-33216 is a medium-severity vulnerability in NVIDIA SNAP-4 Container, published on 24 Mar 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-33216 in the wild and no public exploit code.

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

## Sources

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

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