CVE-2026-3587
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 · uneditedAn unauthenticated remote attacker can exploit a hidden function in the CLI prompt to escape the restricted interface, leading to full compromise of 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 confidenceThis is a CLI (Command Line Interface) vulnerability in network devices where an unauthenticated remote attacker can exploit a hidden function within the CLI prompt to escape the restricted sandboxed interface and gain full administrative control over the device.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 CLI management interface exposureDetermine if the network device's CLI is accessible remotely (telnet, SSH, HTTP-based console) by reviewing device network configuration and listening services. Check device documentation for default management ports (22/SSH, 23/telnet, 80/HTTP).Affected if The CLI is accessible from untrusted networks without access controls.
-
Verify sandboxed CLI restrictionsAccess the CLI and attempt to identify whether you are in a restricted sandboxed environment. Look for indicators such as limited command set, '?' help showing few options, or visual indicators of restricted mode (e.g., 'restricted>', 'user mode'). Document what commands are available versus full administrative commands.Affected if The device offers a sandboxed/restricted CLI mode that can be escaped via hidden functions.
-
Search for hidden or undocumented CLI commandsWithin the CLI, attempt variations of help commands (?, help, <tab>, complete) and probe for hidden functions by entering single characters, numbers, or special characters at the prompt. Compare the available command set against vendor documentation.Affected if Hidden or undocumented CLI functions exist that are not published in official documentation.
-
Review for unexpected privilege escalationCheck current user privileges using commands like 'show privilege', 'whoami', 'show user', or similar. Verify if your session unexpectedly has administrative or root-level access that was not intentionally granted.Affected if An attacker has escaped the sandbox and obtained elevated/administrative privileges.
-
Audit for unauthorized administrative accountsUse CLI commands to list all configured accounts with administrative privileges (e.g., 'show users', 'show accounts', 'show privilege'). Compare against known legitimate administrator accounts documented in your inventory.Affected if Unauthorized accounts with administrative access exist on the device.
-
Examine CLI audit logs for suspicious activityReview device logging, audit trails, or session logs for commands executed from your CLI session, particularly those involving configuration changes, password modifications, or privilege escalation. Look for timestamps or commands you did not issue.Affected if CLI logs show unauthorized configuration changes or commands not issued by legitimate administrators.
A network device with an exposed, sandboxed CLI that contains hidden escape functions, or where unauthorized admin accounts or privilege escalation is observed, indicates the environment is affected by this CVE.
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 dataApply vendor-supplied firmware/software updates immediately as this is a critical unauthenticated remote compromise; if no patch is available, restrict network access to the CLI management interface to trusted IPs only.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3587 — 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-3587 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