dbcve.org
Ac1750 FirmwareOperating system · Tp Link

CVE-2020-10887

CRITICAL · 9.8 CVSS v3.1 Published 2020-03-25
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
This vulnerability allows a firewall bypass on affected installations of TP-Link Archer A7 Firmware Ver: 190726 AC1750 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of IPv6 connections. The issue results from the lack of proper filtering of IPv6 SSH connections. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-9663.

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

This is a firewall bypass vulnerability in TP-Link Archer A7 routers (firmware 190726) where IPv6 SSH connections are not properly filtered, allowing unauthenticated attackers to bypass firewall controls. When chained with other vulnerabilities, this can lead to root-level code execution.

MitigationApply vendor firmware updates if available; otherwise, disable IPv6 at the network edge or implement external firewall rules to filter inbound IPv6 traffic until a patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ac1750 FirmwareOperating system
Affected:= 190726

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Log into the TP-Link router web interface or check the device label to confirm the model is Archer A7 (also marketed as AC1750)
    Affected if Device is not a TP-Link Archer A7/AC1750 router - this vulnerability only affects that specific model
  2. Check firmware version
    In the router web interface, go to Status or System Tools > Firmware Upgrade page to view the current firmware version. Alternatively, check the label on the device or use the TP-Link Tether app.
    Affected if Firmware version is exactly 190726 - this is the only version explicitly listed as affected
  3. Verify IPv6 is enabled
    In the router web interface, navigate to Advanced > IPv6 or Network > IPv6 settings and check if IPv6 is turned ON
    Affected if IPv6 is enabled on the router - the bypass only applies when IPv6 traffic can reach the router
  4. Confirm SSH service is active
    In the router web interface, go to Advanced > Security > Remote Management or similar, and check if SSH management access is enabled for WAN/Internet side
    Affected if SSH management is accessible from the WAN side (Internet) - the vulnerability allows bypassing firewall controls for IPv6 SSH connections
  5. Test IPv6 SSH access from WAN
    Attempt to connect via SSH to the router's public IPv6 address from an external network. Use a command like: ssh -6 user@<router-ipv6-address>
    Affected if SSH connection succeeds over IPv6 when it should be blocked - indicates the firewall bypass is present

You are affected if you have a TP-Link Archer A7/AC1750 router running firmware version 190726 with IPv6 enabled and SSH accessible, allowing unauthenticated IPv6 SSH connections through the firewall.

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

Apply vendor firmware updates if available; otherwise, disable IPv6 at the network edge or implement external firewall rules to filter inbound IPv6 traffic until a patch is released.

Fix this in Ac1750 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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