CVE-2026-3294
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 authentication logic vulnerability in multiple TP-Link range extenders allows an unauthenticated attacker on an adjacent network to manipulate a login parameter and reset the administrator password due to insufficient validation. Successful exploitation allows an attacker to obtain full administrative control of the affected device, potentially impacting on confidentiality, integrity, and availability.
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 confidenceAn authentication logic flaw in TP-Link range extenders allows an unauthenticated attacker on an adjacent network to manipulate a login parameter and reset the administrator password, bypassing authentication entirely and gaining full administrative control of the device.
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< 20260515< 20260515< 20260515< 20260429< 20260515CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 your TP-Link range extender modelLocate the model number on the device label or check the admin web interface (typically accessed at 192.168.0.254 or tplinkrepeater.net) under System or Device InfoAffected if The model is one of: RE305, RE360, RE580d, RE650, or TL-WA860RE
-
Check installed firmware versionIn the web admin interface, navigate to System Tools > Firmware Upgrade or System > Device Info to view the current firmware version numberAffected if The firmware version is earlier than 20260515 for RE305/RE360/RE580d/TL-WA860RE, or earlier than 20260429 for RE650
-
Verify network exposure of the deviceDetermine whether the range extender is on your trusted internal network or accessible from guest networks, IoT VLANs, or other adjacent network segments where untrusted devices could resideAffected if The device is accessible from any network segment other than your fully trusted LAN
-
Confirm web management interface accessibilityCheck if the admin web interface is reachable from network interfaces beyond the primary LAN (such as from guest networks or secondary wireless networks created by the extender)Affected if Management interface is accessible from networks other than the main trusted LAN
You are affected if you have a TP-Link RE305, RE360, RE580d, RE650, or TL-WA860RE device running firmware below the specified version AND the device is reachable from an adjacent or untrusted network segment.
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.
dbcve · scoped2026042920260515
Apply vendor-supplied firmware updates when available; until then, restrict network access to the device's management interface to trusted users only and consider network segmentation to limit adjacent network exposure.
Firmware version 20260515 (or later) for Re305/Re360/Re580d/TL-WA860RE; version 20260429 (or later) for Re650
- 1. Identify the specific TP-Link range extender model (Re305, Re360, Re580d, Re650, or TL-WA860RE) in your environment
- 2. Check the current firmware version of the affected device through the device's web management interface or TP-Link Tether app
- 3. For Re305, Re360, Re580d, and TL-WA860RE: Upgrade firmware to version 20260515 or later
- 4. For Re650: Upgrade firmware to version 20260429 or later
- 5. Download firmware only from the official TP-Link support website (support.tp-link.com) using your exact model number
- 6. Access the device's management interface, navigate to the Firmware Upgrade section, and upload the downloaded firmware file
- 7. After upgrade, verify the new firmware version is installed and change the administrator password as a precaution
- 8. Check TP-Link's security advisory page periodically for any additional guidance
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3294 — 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-3294 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