Tl-wr841nd Firmware
7 CVEs tracked. 3 of them are in CISA KEV.
This hub aggregates every CVE we track for Tl-wr841nd Firmware, a product in the networking infrastructure space. Use it to gauge the current risk picture and drill into individual advisories.
Tl-wr841nd Firmware CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 3 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 1 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 7 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High5
- Medium2
Latest CVEs
The 7 most recently published vulnerabilities affecting Tl-wr841nd Firmware.
- CVE-2025-9377Authenticated RCE via Parental Control command injection7.2
- CVE-2025-25901A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11, triggered by the dnsserver1 and dnsserver2 parameters at /userRpm/WanSlaacCfgRpm.htm. This vulnerability allows attackers t...7.5
- CVE-2025-25897A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11 via the 'ip' parameter at /userRpm/WanStaticIpV6CfgRpm.htm. This vulnerability allows attackers to cause a Denial of Service...7.5
- CVE-2025-25898A buffer overflow vulnerability was discovered in TP-Link TL-WR841ND V11 via the pskSecret parameter at /userRpm/WlanSecurityRpm.htm. This vulnerability allows attackers to cause a Denial of Servic...7.5
- CVE-2024-9284TP-LINK TL-WR841ND popupSiteSurveyRpm.htm stack-based overflow6.5
- CVE-2023-50224TP-Link TL-WR841N dropbearpwd Improper Authentication Information Disclosure Vulnerability6.5
- CVE-2015-3035Directory traversal vulnerability in TP-LINK Archer C5 (1.2) with firmware before 150317, C7 (2.0) with firmware before 150304, and C8 (1.0) with firmware before 150316, Archer C9 (1.0), TL-WDR3500...7.5
Product grouping is registry-driven, with AI assist and human review. How it works