Skip to content
Applications

CVE-2025-59107

8.5
High
EPSS 0.16%Jan 26, 2026

Static ZIP decrypt password in Dormakaba FWServiceTool firmware updates.

common questions

Is CVE-2025-59107 being exploited?

Not confirmed. CVE-2025-59107 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.16% probability of exploitation in the next 30 days.

How severe is CVE-2025-59107?

CVE-2025-59107 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-59107?

Not known from our data. No patch reference has been recorded for CVE-2025-59107, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-59107 affect?

CVE-2025-59107 affects Dormakaba FWServiceTool, Dormakaba Access Manager firmware updates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-59107?

Limit FW update access; verify firmware integrity; request patch.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Dormakaba FWServiceToolDormakaba Access Manager firmware updates
impact

Network attacker can decrypt firmware ZIP, tamper updates, risking malicious firmware deployment to Access Managers.

action required

Immediate action required

affected versions
dormakaba Access Manager 92xx-k5
  • affectedAll versions

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free