dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-8286

CRITICAL · 9.3 CVSS v4.0 Published 2025-07-31
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 affected products expose an unauthenticated Telnet-based command line interface that could allow an attacker to modify hardware configurations, manipulate data, or factory reset the device.

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

A critical unauthenticated Telnet-based command line interface is exposed in affected network devices, allowing remote attackers to connect without credentials and execute commands that can modify hardware configurations, manipulate stored data, or perform factory resets.

MitigationDisable the unauthenticated Telnet service on all affected devices, restrict Telnet access at network boundaries using firewalls, and replace with authenticated and encrypted alternatives such as SSH.

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:N/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. Check if Telnet service is listening
    Run 'netstat -tuln | grep 23' or 'ss -tuln | grep 23' to see if port 23 (Telnet) is open and listening on any interface
    Affected if Port 23 is open and listening on a reachable network interface (especially WAN/external)
  2. Identify Telnet service banner
    Connect to the Telnet port using 'telnet <target-ip> 23' or 'nc -nv <target-ip> 23' and observe the banner/prompt response without providing credentials
    Affected if The service presents a command prompt or banner without prompting for username/password authentication
  3. Test for unauthenticated command execution
    Try issuing basic commands (like 'help', '?', 'show version', or enter) via the Telnet connection without logging in
    Affected if Commands execute and return output without requiring any login credentials
  4. Verify authentication configuration
    Check the product documentation or configuration files for 'telnet auth', 'telnet enable', or 'authentication required' settings - look for 'no authentication' or 'disabled' states
    Affected if Telnet service is configured to not require authentication or has authentication explicitly disabled
  5. Check product version against advisory
    Obtain the device firmware/software version via 'show version', 'ver', or system information pages, then compare to any vendor-released affected version lists
    Affected if The installed version matches or falls within an affected version range if specified by the vendor

You are affected if a Telnet service is exposed on your system and accepts commands without requiring any authentication 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

Disable the unauthenticated Telnet service on all affected devices, restrict Telnet access at network boundaries using firewalls, and replace with authenticated and encrypted alternatives such as SSH.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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