VulnerabilityPublished 28 Aug 2025

CVE-2025-57217: Tenda AC10 · Stack-based Buffer Overflow

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Immediate mitigation involves isolating the affected Tenda AC10 v4.0 routers from untrusted networks, especially the internet-facing interfaces, to reduce exposure to remote exploitation attempts.
Network administrators should monitor router logs and network traffic for unusual activity or repeated connection attempts targeting the router's management interface.
Disable remote management features if enabled, or restrict access to trusted IP addresses only.
Implement network segmentation to ensure that critical systems are not dependent on a single vulnerable router.
Regularly check for firmware updates from Tenda, and apply patches promptly once available.
Consider replacing affected routers with models from vendors with a stronger security track record if patches are delayed.
Employ intrusion detection/prevention systems (IDS/IPS) with signatures for buffer overflow attempts targeting router management interfaces.
Educate users and IT staff about the risks of using outdated firmware and the importance of timely updates. These steps go beyond generic advice by focusing on network architecture adjustments, access control, and proactive monitoring specific to the affected device and vulnerability.

Description

Tenda AC10 v4.0 firmware v16.03.10.09_multi_TDE01 was discovered to contain a stack overflow via the Password parameter in the function R7WebsSecurityHandler.

Impact

For European organizations, the primary impact of CVE-2025-57217 is the potential disruption of network availability due to router crashes or reboots caused by exploitation of the stack overflow. This could affect small to medium enterprises (SMEs) and home office setups that use the Tenda AC10 v4.0 router, leading to temporary loss of internet connectivity and productivity interruptions. While the vulnerability does not directly compromise data confidentiality or integrity, availability issues can indirectly affect business operations, especially for organizations relying on continuous internet access for cloud services, VoIP communications, or remote work. Critical infrastructure or larger enterprises are less likely to be affected unless they use this consumer-grade router model in less secure network segments. The absence of known exploits reduces immediate risk, but the ease of exploitation and network exposure means attackers could develop exploits, especially in botnet or DoS attack campaigns. European organizations should be aware of this vulnerability as part of their network device risk management and incident response planning.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

plaid-knot-11b.notion.site/Stack-Buffer-Overflow-in-login-Auth-via-Password-parameter-Remote-attacker-can-execute-arbitrary-c-23fb3e9cce32800ba969f8b3a9f80bda?source=copy_link (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Sep 2025, 18:33 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats