dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-59107

HIGH · 8.5 CVSS v4.0 Published 2026-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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
Dormakaba provides the software FWServiceTool to update the firmware version of the Access Managers via the network. The firmware in some instances is provided in an encrypted ZIP file. Within this tool, the password used to decrypt the ZIP and extract the firmware is set statically and can be extracted. This password was valid for multiple observed firmware versions.

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

The Dormakaba FWServiceTool uses a statically embedded password to decrypt encrypted ZIP files containing firmware for Access Managers. This password is hardcoded within the tool and can be extracted by anyone with access to the tool binary, enabling unauthorized decryption of firmware updates.

MitigationReplace the static password with dynamic credential management such as per-customer keys, asymmetric encryption, or a secure key exchange protocol. Rotate any exposed passwords and implement proper secrets management.

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

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 if FWServiceTool is installed in your environment
    Search for the FWServiceTool executable or installation directory on systems used for firmware management. Common locations include C:\Program Files\Dormakaba\ or similar program directories, or search for files containing 'FWServiceTool' in the name.
    Affected if FWServiceTool is found on any system used for Access Manager device management
  2. Confirm use of Dormakaba Access Manager devices
    Inventory network devices or review hardware asset records for Dormakaba Access Manager or related access control devices manufactured by Dormakaba.
    Affected if Dormakaba Access Manager devices are deployed in the environment
  3. Check firmware version on Access Manager devices
    Access the device management interface or use Dormakaba administrative tools to retrieve the current firmware version of Access Manager devices. Compare against any firmware versions released prior to the patch date for this CVE.
    Affected if Firmware version is older than the patched version released by Dormakaba for this issue
  4. Determine if firmware updates were performed using FWServiceTool
    Review logs, change management records, or administrative procedures to identify if the FWServiceTool was used to apply or decrypt firmware updates for Access Manager devices.
    Affected if FWServiceTool was used to process or apply firmware to Access Manager devices
  5. Inspect tool binary for static credentials
    If FWServiceTool is available, examine the executable or associated configuration files for hardcoded password strings. Use strings extraction tools or hex editors to search for password patterns in the tool binaries.
    Affected if Static passwords or hardcoded credential strings are found within the FWServiceTool binary or its configuration files

Your environment is affected if you have deployed Dormakaba Access Manager devices and have used the FWServiceTool to process firmware, particularly with firmware versions predating the patched release.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace the static password with dynamic credential management such as per-customer keys, asymmetric encryption, or a secure key exchange protocol. Rotate any exposed passwords and implement proper secrets management.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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