dbcve.org
CWE-1391Weakness · CWE-1391

CVE-2025-59103

CRITICAL · 9.2 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 →
100/100
Remediation priority · Urgent
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
The Access Manager 92xx in hardware revision K7 is based on Linux instead of Windows CE embedded in older hardware revisions. In this new hardware revision it was noticed that an SSH service is exposed on port 22. By analyzing the firmware of the devices, it was noticed that there are two users with hardcoded and weak passwords that can be used to access the devices via SSH. The passwords can be also guessed very easily. The password of at least one user is set to a random value after the first deployment, with the restriction that the password is only randomized if the configured date is prior to 2022. Therefore, under certain circumstances, the passwords are not randomized. For example, if the clock is never set on the device, the battery of the clock module has been changed, the Access Manager has been factory reset and has not received a time yet.

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 Access Manager 92xx K7 hardware revision runs Linux and exposes an SSH service on port 22 with two hardcoded, easily guessable user accounts. The password randomization mechanism only triggers if the device's configured date is prior to 2022, leaving devices vulnerable when the clock is unset, battery-replaced, or factory-reset without time synchronization.

MitigationImmediately change default SSH credentials, ensure NTP/time synchronization is configured so the date is post-2021 to enable password randomization, disable SSH if unused, and restrict network access to port 22 via firewall rules.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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 device model and hardware revision
    Access the device management interface or check the physical device label to confirm it is an Access Manager 92xx with hardware revision K7. Alternatively, query the device via SSH or console and run commands like 'cat /proc/cpuinfo' or check boot logs for model identification.
    Affected if Device is not an Access Manager 92xx hardware revision K7 - this vulnerability does not apply.
  2. Verify SSH service is enabled on port 22
    Run a port scan against the device or use 'nc -z <device_ip> 22' or 'nmap -p 22 <device_ip>' to confirm port 22 is open and responding. Check device config for SSH service status if you have administrative access.
    Affected if SSH is not enabled or port 22 is closed - the credential flaw cannot be exploited remotely.
  3. Check system date and time
    If you have SSH or console access, run 'date' or 'hwclock' to check the current system clock. Look for a date prior to 2022, or dates like 1970, 1980, 2000, or clearly uninitialized timestamps indicating a failed or absent time sync.
    Affected if System date is post-2021 - password randomization should be active and default credentials should be changed.
  4. Test for default weak credentials
    Attempt to SSH into the device using the known default credentials referenced in CVE-2025-59103 (the two hardcoded weak user accounts). If login succeeds with these credentials, the device is confirmed vulnerable.
    Affected if Default credentials are accepted - the device clock was not properly initialized and default weak passwords remain active.

Device is affected if it is an Access Manager 92xx K7, has SSH enabled on port 22, and has a system clock showing a date prior to 2022 (or uninitialized), allowing login with hardcoded default credentials.

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

Immediately change default SSH credentials, ensure NTP/time synchronization is configured so the date is post-2021 to enable password randomization, disable SSH if unused, and restrict network access to port 22 via firewall rules.

Have this fixed 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 help mitigating

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-2025-59103 — 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-59103 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