dbcve.org
VisionlineApplication · Assaabloy

CVE-2026-3315

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.34.0 or later.
See remediation →
80/100
Remediation priority · High
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
Incorrect Default Permissions, : Execution with Unnecessary Privileges, : Incorrect Permission Assignment for Critical Resource vulnerability in ASSA ABLOY Visionline on Windows allows Configuration/Environment Manipulation.This issue affects Visionline: from 1.0 before 1.33.

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

ASSA ABLOY Visionline on Windows installs with incorrect default file system permissions, allowing local unprivileged users to modify configuration files or executable paths. This enables privilege escalation to execute code with elevated (administrator/SYSTEM) privileges due to improper permission assignments on critical resources.

MitigationUpdate Visionline to version 1.33 or later which contains corrected default permissions. For existing installations, audit and remediate file/folder permissions on the Visionline installation directory to remove excessive user/group access.

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
VisionlineApplication
Affected:>= 1.0.0, < 1.34.0

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Find Visionline installation path and version
    Locate the Visionline installation directory (commonly C:\Program Files\ASSA ABLOY\Visionline or C:\Program Files (x86)\ASSA ABLOY\Visionline). Check the version by right-clicking the executable (Visionline.exe), selecting Properties, and viewing the Details tab for Product Version.
    Affected if Installed version is 1.0.0 or higher but lower than 1.34.0
  2. Verify unprivileged user write access to installation folder
    Open the Visionline installation folder in Windows Explorer, right-click the folder, select Properties, go to the Security tab, and check the permissions for Users or Authenticated Users groups. Alternatively, run 'icacls "C:\Program Files\ASSA ABLOY\Visionline"' from an unprivileged command prompt to see effective permissions.
    Affected if Users or non-admin accounts have Write or Modify permissions on the Visionline installation directory
  3. Check configuration file permissions
    Navigate to the Visionline installation folder and examine permissions on configuration files (look for .ini, .xml, .cfg, or .config files). Use 'icacls <filename>' to check if Users group has Write or Modify access to these files.
    Affected if Unprivileged users can modify or overwrite configuration files in the installation directory
  4. Verify executable path integrity
    Review permissions on the main executable files (Visionline.exe and related .exe files) in the installation folder. Check if Users group has Write or Modify permissions that would allow replacing the executable.
    Affected if Non-administrator accounts have Write or Modify permissions on executable files in the Visionline folder

A system is affected if Visionline version is 1.0.0 through 1.33.x and unprivileged local users have Write or Modify permissions on the Visionline installation directory, its configuration files, 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.34.0 or later
Fixed in 1.34.0
Interim mitigation

Update Visionline to version 1.33 or later which contains corrected default permissions. For existing installations, audit and remediate file/folder permissions on the Visionline installation directory to remove excessive user/group access.

Recommended fix Moderate confidence

Visionline 1.34.0 or later

  1. 1. Identify the currently installed Visionline version on the affected Windows system
  2. 2. Create a backup of the Visionline configuration and any critical data
  3. 3. Download Visionline version 1.34.0 or later from the official vendor source (www.vingcard.com)
  4. 4. Execute the installer with appropriate privileges to perform the upgrade
  5. 5. Verify the upgrade completed successfully by checking the installed version
  6. 6. Confirm the application launches and functions properly with the new version

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

Fix this in Visionline Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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