dbcve.org
Securebrowser For OnegateApplication · Soliton

CVE-2026-27653

MEDIUM · 6.7 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 1.4.8 / 2.0.15 or later.
See remediation →
67/100
Remediation priority · Elevated

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
The installers for multiple products provided by Soliton Systems K.K. contain an issue with incorrect default permissions, which may allow arbitrary code to be executed with SYSTEM privileges.

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 · moderate confidence

The installers for Soliton Systems K.K. products create files or directories with overly permissive default permissions (likely world-writable or with weak ACLs), allowing a local unprivileged attacker to modify executable files or DLLs and achieve arbitrary code execution with SYSTEM privileges.

MitigationIdentify all installed files from affected Soliton products and correct file permissions to follow least-privilege principles—remove write access for non-admin users on executable directories and re-install products with secure permission configurations if needed.

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
Securebrowser For OnegateApplication
Affected:= 1.0.0
Securebrowser IiApplication
Affected:>= 2.0.0, < 2.0.15
SecureworkspaceApplication
Affected:>= 1.0.0, < 1.4.8

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
Local
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Soliton product installations
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Soliton Securebrowser' or 'Soliton Secureworkspace', or look in common installation paths like C:\Program Files\Soliton or C:\Program Files (x86)\Soliton
    Affected if Any Soliton Securebrowser for Onegate, Securebrowser Ii, or Secureworkspace entry is found in the registry or filesystem
  2. Determine installed version
    For each Soliton product found, read the DisplayVersion value from the registry uninstall key, or check the version info of the main executable (typically securebrowser.exe, securebrowser_ii.exe, or secureworkspace.exe) in the installation directory
    Affected if The version is 1.0.0 for Securebrowser For Onegate, between 2.0.0 and 2.0.14 for Securebrowser Ii, or between 1.0.0 and 1.4.7 for Secureworkspace
  3. Check installation directory permissions
    Right-click the main installation folder (e.g., C:\Program Files\Soliton\Securebrowser or Secureworkspace), select Properties, go to the Security tab, and examine which users or groups have Write or Modify permissions
    Affected if Users other than Administrators or SYSTEM have Write or Modify access to the installation directory containing executable files or DLLs
  4. Verify executable file permissions
    Right-click the main executable files (.exe and .dll files) in the Soliton installation folder, select Properties, Security, and check if non-admin users have Write permission
    Affected if Non-privileged users have Write permission on executable files or DLLs in the Soliton installation directory

A user is affected if any Soliton Securebrowser or Secureworkspace product is installed with a vulnerable version AND non-administrative users have Write access to the installation directory or its executable files.

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.4.8 / 2.0.15 or later
Fixed in 1.4.82.0.15
Interim mitigation

Identify all installed files from affected Soliton products and correct file permissions to follow least-privilege principles—remove write access for non-admin users on executable directories and re-install products with secure permission configurations if needed.

Recommended fix High confidence

Securebrowser II: 2.0.15; Secureworkspace: 1.4.8; Securebrowser For Onegate: any version > 1.0.0

  1. 1. Identify which Soliton product(s) are deployed in your environment: Securebrowser For Onegate, Securebrowser II, or Secureworkspace
  2. 2. For Securebrowser For Onegate: Upgrade from version 1.0.0 to a newer version (any version after 1.0.0 contains the fix)
  3. 3. For Securebrowser II: Upgrade from any version >= 2.0.0 and < 2.0.15 to version 2.0.15 or later
  4. 4. For Secureworkspace: Upgrade from any version >= 1.0.0 and < 1.4.8 to version 1.4.8 or later
  5. 5. Verify the upgrade was successful by checking the product version
  6. 6. Re-run the installer or reinstall the product to ensure correct file permissions are applied
Caveat Review release notes for any functional changes between your current version and the upgrade version

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

Fix this in Securebrowser For Onegate Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27653 — 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-27653 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