Skip to content
IoT

CVE-2026-75616

8.5
High
EPSS 3%Patch availableAug 21, 2026

Authenticated OS command injection in Archer C20 v6 web interface allowing device takeover.

common questions

Is CVE-2026-75616 being exploited?

Not confirmed. CVE-2026-75616 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 3.1% probability of exploitation in the next 30 days.

How severe is CVE-2026-75616?

CVE-2026-75616 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-75616?

Yes. A fix has been recorded for CVE-2026-75616. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-75616 affect?

CVE-2026-75616 affects TP-Link Archer C20 v6 (router firmware v6). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-75616?

Harden admin access, isolate device, change creds; apply vendor firmware patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TP-Link Archer C20 v6 (router firmware v6)
impact

Authenticated administrator can execute arbitrary system commands, enabling full device compromise, traffic interception, persistent backdoors and network pivoting.

action required

Immediate action required

affected versions
TP-Link Systems Inc. Archer C20 v6
  • affected< EU_0.9.1 Build 260811
  • affected< US_0.9.1 Build 260812
  • affected< RU_0.9.1 Build 260812

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free