CVE-2026-25715
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 · uneditedThe web management interface of the device allows the administrator username and password to be set to blank values. Once applied, the device permits authentication with empty credentials over the web management interface and Telnet service. This effectively disables authentication across all critical management channels, allowing any network-adjacent attacker to gain full administrative control without credentials.
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 confidenceThe web management interface of the device contains a flaw allowing administrator username and password to be set to blank/empty values. When empty credentials are applied, the device accepts authentication with null credentials across both the web management interface and Telnet service, effectively disabling authentication and allowing any network-adjacent attacker full administrative access.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Inspect web management interface user configurationLog into the device's web management interface and navigate to the administrative user account settings. Examine whether the username and password fields can be set to blank or empty values. If the interface permits saving empty credentials, the device is vulnerable.Affected if The administrative account can be configured with a blank or empty username and/or password
-
Test web interface authentication with null credentialsAttempt to authenticate to the web management interface using no username and no password (or blank fields). Observe whether the login attempt succeeds and grants administrative access.Affected if Authentication succeeds with blank/empty credentials, indicating the vulnerability is exploitable
-
Test Telnet service authentication with null credentialsConnect to the device via Telnet (typically port 23) and attempt to log in with no username and no password when prompted. Record whether access is granted.Affected if Telnet login succeeds with blank/empty credentials, indicating the authentication bypass affects Telnet as well
-
Review device configuration for empty password entriesIf the device configuration can be exported or accessed (via backup file, API, or CLI), examine user account records for any entries where the password field is empty, null, or contains no characters.Affected if Any administrative user account has an empty or null password field in the configuration
-
Check if Telnet service is enabled and exposedFrom a network perspective, determine if Telnet port 23 is open and reachable on the device. Use port scanning or check the device's service configuration to confirm Telnet availability.Affected if Telnet is enabled and accessible on the device, making it vulnerable to the null credential attack vector
The environment is affected if any administrative account can be configured with blank credentials or if authentication with empty credentials succeeds on either the web interface or Telnet.
Generated from the published advisory. Verify against your own configuration.
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 dataAdministrators should immediately verify that no accounts have blank credentials configured and reset any affected accounts to strong, non-empty credentials. If the device allows this configuration, contact the vendor for a firmware update that enforces minimum credential requirements, and consider disabling Telnet in favor of SSH.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25715 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25715 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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