# CVE-2025-46713: Sandboxie has Pool Buffer Overflow in SbieDrv.sys API (API_SET_SECURE_PARAM)

> An integer overflow in Sandboxie's driver allows buffer overflows, potentially enabling code execution or privilege escalation on Windows systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 22 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-5g85-6p6v-r479

## What is CVE-2025-46713?

CVE-2025-46713 is a high-severity vulnerability in sandboxie-plus Sandboxie, published on 22 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sandboxie is a sandbox-based isolation software for 32-bit and 64-bit Windows NT-based operating systems. Starting in version 0.0.1 and prior to 1.15.12, API_SET_SECURE_PARAM may have an arithmetic overflow deep in the memory allocation subsystem that would lead to a smaller allocation than requested, and a buffer overflow. Version 1.15.12 fixes the issue.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Sandboxie-Plus Sandboxie.

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

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

## Is CVE-2025-46713 being exploited?

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

## Other vulnerabilities in sandboxie-plus Sandboxie

- [CVE-2018-18748](https://insights.sbomify.com/CVE-2018-18748/): Security feature bypass in n/a (critical 10.0)
- [CVE-2025-64721](https://insights.sbomify.com/CVE-2025-64721/): Sandboxie's Integer Overflow in SbieIniServer::RC4Crypt allows sandbox escape and SYSTEM compromise (critical 9.9)
- [CVE-2026-34458](https://insights.sbomify.com/CVE-2026-34458/): Sandboxie-Plus privilege escalation via INI CRLF injection bypassing EditAdminOnly (critical 9.3)
- [CVE-2024-49360](https://insights.sbomify.com/CVE-2024-49360/): Path traversal in Sandboxie (critical 9.2)
- [CVE-2026-34459](https://insights.sbomify.com/CVE-2026-34459/): Sandboxie-Plus sandbox escape via uninitialized memory leak and stack overflow in GetRawInputDeviceInfoSlave (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46713 is a high-severity vulnerability in sandboxie-plus Sandboxie, published on 22 May 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-46713 in the wild and no public exploit code.

Affected product: sandboxie-plus Sandboxie. 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-46713/ (Markdown: https://insights.sbomify.com/CVE-2025-46713/index.md)
```

## Sources

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

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