CVE
Sandboxie privilege escalation to SYSTEM in SbieSvc
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 1.18.6
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Sandboxie-Plus before 1.18.6 (affected versions <= 1.18.5). A running signed Sandboxie process (e.g., SandMan.exe) under the attacker's user account must be available for code injection.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Sandboxie-Plus, a sandboxing tool, is affected. A local attacker with a standard user account can use the SbieSvc service to run UpdUtil.exe as SYSTEM, inject code into a signed SandMan.exe process to get past the signature check, and write attacker-controlled files to arbitrary paths, which can lead to full SYSTEM code execution.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Sandboxie-Plus before 1.18.6 contains a local privilege escalation vulnerability in SbieSvc that allows standard users to launch UpdUtil.exe as SYSTEM via MSGID_PROCESS_RUN_UPDATER requests. Attackers can inject code into a signed SandMan.exe process to bypass the signature check and write attacker-controlled files to arbitrary paths, achieving SYSTEM code execution.
Who should check
Teams running Sandboxie-Plus 1.18.5 or earlier on Windows, especially hosts where standard users run Sandboxie.
“Sandboxie-Plus before 1.18.6 contains a local privilege escalation vulnerability in SbieSvc”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Sandboxie-Plus before 1.18.6 (affected versions <= 1.18.5). A running signed Sandboxie process (e.g., SandMan.exe) under the attacker's user account must be available for code injection.Upgrade to a fixed version: 1.18.6.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129956 (Sandboxie-Plus before 1.18.6 Privilege Escalation via SbieSvc MSGID_PROCESS_RUN_UPDATER), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129956 (entry last updated 2026-11-16):
Affected:
- sandboxie-plus Sandboxie: fixed in 1.18.6
Fixed versions: 1.18.6.
Conditions (all must be true for the bug to be hit):
- Sandboxie-Plus before 1.18.6 (affected versions <= 1.18.5). (source: https://www.vulncheck.com/advisories/sandboxie-plus-before-1.18.6-privilege-escalation-via-sbiesvc-msgid-process-run-updater)
- A running signed Sandboxie process (e.g., SandMan.exe) under the attacker's user account must be available for code injection. (source: https://github.com/sandboxie-plus/Sandboxie/security/advisories/GHSA-46vh-v2q6-wrcv)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
CISA KEV: CVE-2026-129956 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129956 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/sandboxie-plus/Sandboxie/security/advisories/GHSA-46vh-v2q6-wrcv
- https://github.com/sandboxie-plus/Sandboxie/commit/4e121cc4dacdc31973adcb81581b0414d48c26fc
- https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.18.6
- https://github.com/sandboxie-plus/Sandboxie/blob/v1.18.5/Sandboxie/core/svc/ProcessServer.cpp#L1519-L1611
- https://github.com/sandboxie-plus/Sandboxie/blob/v1.18.5/SandboxieTools/UpdUtil/UpdUtil.cpp#L1349-L1386
- https://www.vulncheck.com/advisories/sandboxie-plus-before-1.18.6-privilege-escalation-via-sbiesvc-msgid-process-run-updater
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129956
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129956"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- sandboxie-plus Sandboxie
fixed in 1.18.6
Evidence 8
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Repository
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129956
Is CVE-2026-129956 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A standard local user can abuse SbieSvc, the Sandboxie service, to run arbitrary code as NT AUTHORITY\SYSTEM, which gives full control of the machine. The flaw works by injecting code into a running signed Sandboxie process such as SandMan.exe, which runs as the current user.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-129956?
Sandboxie: before 1.18.6.Source: cve.now feed data
Am I affected, and how do I check?
Sandboxie-Plus versions up to and including 1.18.5 are affected, since the fix ships in 1.18.6. To check a version, open the Sandboxie-Plus about dialog or look at the installed version in the program's properties. The bug needs a local user account with access to a running signed Sandboxie process, such as SandMan.exe, for code injection.Source: vulncheck.com, github.com
How do I fix CVE-2026-129956?
Upgrade Sandboxie-Plus to version 1.18.6 or later, which is the fixed release listed for this vulnerability.Source: vulncheck.com, github.com