dbcve.org
SandboxieApplication · Sandboxie Plus

CVE-2026-34527

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 1.17.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Sandboxie-Plus is an open source sandbox-based isolation software for Windows. In versions 1.17.2 and earlier, SbieIniServer::HashPassword converts a SHA-1 digest to hexadecimal incorrectly. The high nibble of each byte is shifted right by 8 instead of 4, which always produces zero for an 8-bit value. As a result, the stored EditPassword hash only preserves the low nibble of each digest byte, reducing the effective entropy from 160 bits to 80 bits. This is layered on top of an unsalted SHA-1 scheme. The reduced entropy makes leaked or backed-up password hashes materially easier to brute-force. This issue has been fixed in version 1.17.3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Sandboxie-Plus versions 1.17.2 and earlier, the SbieIniServer::HashPassword function contains a bit-shift bug during SHA-1 digest-to-hexadecimal conversion. The code shifts the high nibble right by 8 bits instead of 4, producing zero for all high nibbles and preserving only the low nibble of each byte. This reduces effective password hash entropy from 160 bits to 80 bits, combined with an unsalted SHA-1 scheme, making brute-force attacks significantly easier.

MitigationUpgrade to Sandboxie-Plus version 1.17.3 or later to obtain the corrected password hashing implementation. Consider changing any passwords set using versions 1.17.2 or earlier as a precautionary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SandboxieApplication
Affected:< 1.17.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Sandboxie Plus version
    Open the Sandboxie Plus application and locate the version number in the About section, or run the executable with a version flag if available
    Affected if The version shown is 1.17.2 or earlier (versions prior to 1.17.3 contain the flaw)
  2. Confirm password protection is in use
    Check if a master password or PIN has been configured for Sandboxie Plus in the application settings under Password or Security options
    Affected if A password or PIN is set - the flawed HashPassword function is only invoked when password protection is enabled
  3. Locate password configuration storage
    Find the configuration file where Sandboxie Plus stores password hashes, typically in the installation directory or user profile configuration folder
    Affected if Password hashes exist in the configuration - the flawed implementation affects any stored hashes

You are affected if you are running Sandboxie Plus version 1.17.2 or earlier and have enabled password protection, as the HashPassword function bug only impacts environments where a password has been configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.17.3 or later
Fixed in 1.17.3
Interim mitigation

Upgrade to Sandboxie-Plus version 1.17.3 or later to obtain the corrected password hashing implementation. Consider changing any passwords set using versions 1.17.2 or earlier as a precautionary measure.

Recommended fix High confidence

Sandboxie-Plus 1.17.3

  1. Download Sandboxie-Plus version 1.17.3 or later from the official GitHub releases or project website
  2. Run the installer and follow the upgrade prompts to update your existing Sandboxie installation
  3. After installation, verify the version by checking the installed version number to confirm you are on 1.17.3 or higher
  4. If you have any custom configurations or saved settings, review them after the upgrade to ensure they function correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sandboxie Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA0.5 h
3.5 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34527 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34527 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data