CVE-2026-10045
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 · uneditedShenzhen Kangda Xin Intelligent Network Technology Company's router, model DR300, version 2.1.2.121, contains hardcoded login credentials and has telnet enabled by default on WAN and LAN interfaces. These vulnerabilities allow attackers to read and write to memory, modify firmware stored in flash, inspect active connections, and view currently connected devices.
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 DR300 router firmware contains hardcoded credentials and has telnet service exposed on both WAN and LAN interfaces by default. This critical combination allows remote attackers to authenticate using the hardcoded credentials via telnet and gain privileged access to read/write memory, modify firmware in flash, inspect network connections, and view connected devices.
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.
-
Identify the router modelAccess the router administration panel (typically via web browser at 192.168.0.1 or 192.168.1.1) or check the physical device label to confirm the model is DR300Affected if The device is not a DR300 router, then it is not affected by this specific CVE
-
Check the firmware versionIn the router admin panel, navigate to System Status or Firmware Upgrade section to view the installed firmware version; alternatively, check the version displayed on the device label or via telnet if already accessibleAffected if The firmware version is 2.1.2.121 - this is the affected version listed in the CVE
-
Verify telnet service status on LANIn the router admin panel, look for Services, Security, or Firewall settings and check if Telnet server is enabled for the LAN interface; on some devices this may appear under 'Remote Management' or 'Access Control'Affected if Telnet is enabled on the LAN interface, the vulnerability is exploitable from inside the local network
-
Confirm default credentials are in useAttempt to log into the telnet service (port 23) using common default credentials such as admin/admin, admin/password, or root/root; or check if the router has not had its administrative password changed from factory defaultsAffected if The default hardcoded credentials are still active, remote unauthenticated access is possible
The device is affected if it is a DR300 router running firmware version 2.1.2.121 AND telnet is enabled on either the LAN or WAN interface with the default hardcoded credentials still in place.
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 dataImmediately disable telnet on all interfaces and change any hardcoded credentials; if the vendor does not provide a firmware patch, replace the device with a supported model from a vendor that provides regular security updates.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10045 — 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-10045 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