dbcve.org
Tl Wr841n FirmwareOperating system · Tp Link

CVE-2026-9105

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-29
Fix available
A fix is available. Upgrade to 14_260518 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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
An authenticated stack-based buffer overflow vulnerability exists in the web management interface of TP-Link TL-WR841N v14. A remote authenticated attacker can send crafted HTTP requests to cause the embedded web server to overflow a stack buffer, resulting in a crash of the affected process. Successful exploitation results in a denial-of-service condition, causing the device to crash and automatically reboot.

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

Authenticated stack-based buffer overflow in the HTTP server of TP-Link TL-WR841N v14 allows a remote authenticated attacker to overflow a stack buffer via crafted HTTP requests, causing process crash and device auto-reboot resulting in denial of service.

MitigationAs the device is end-of-life with no vendor patch available, mitigate by isolating the device on a restricted network segment, disabling remote management access from the internet, and replacing with a supported router model.

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
Tl Wr841n FirmwareOperating system
Affected:< 14_260518

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 the router model
    Log into the router web interface or check the device label to confirm the exact model is TP-Link TL-WR841N version 14
    Affected if The device is not a TP-Link TL-WR841N v14
  2. Check the installed firmware version
    Access the router admin panel, typically at 192.168.0.1, navigate to System Tools > Firmware Upgrade or Status page, and record the firmware version string
    Affected if Firmware version is earlier than 14_260518 (e.g., 14_xxxxxx with a date before May 18, 2016)
  3. Confirm HTTP server is enabled
    In the router web interface, go to Security > Remote Management or similar section and verify the HTTP management interface is turned on
    Affected if The HTTP server/management interface is enabled on the device
  4. Check exposure to external networks
    Determine if the router's management interface is accessible from the internet by attempting to access the router's WAN IP on port 80 from an external location, or by checking port forwarding/firewall rules
    Affected if Remote HTTP management is accessible from the internet (WAN side)
  5. Verify authentication is required
    Confirm that the router requires login credentials to access the web interface and that default admin credentials have not been changed
    Affected if The device allows unauthenticated access to the management interface

You are affected if you own a TL-WR841N v14 with firmware below version 14_260518 and have the HTTP management interface enabled, especially if exposed to the internet.

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.

dbcve · scoped
Upgrade available Upgrade to 14_260518 or later
Fixed in 14_260518
Interim mitigation

As the device is end-of-life with no vendor patch available, mitigate by isolating the device on a restricted network segment, disabling remote management access from the internet, and replacing with a supported router model.

Recommended fix High confidence

TP-Link TL-WR841N v14 firmware version 14_260518 or later

  1. Download firmware version 14_260518 or later for TP-Link TL-WR841N v14 from the official TP-Link support website (www.tp-link.com)
  2. Log in to the device's web management interface
  3. Navigate to the 'System Tools' > 'Firmware Upgrade' (or similar section)
  4. Click 'Choose File' and select the downloaded firmware file
  5. Click 'Upgrade' to apply the firmware
  6. Wait for the upgrade process to complete - do not power off the device
  7. The device will automatically reboot after the upgrade completes
  8. Verify the firmware version has been updated in the web interface

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tl Wr841n Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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