CVE-2025-70747VulnerabilityPublished 14 Jan 2026

CVE-2025-70747: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% 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:H

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

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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 2026
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 2026-10-25.

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 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

1. Immediately restrict access to the Tenda AX-1806 router management interfaces by limiting them to trusted internal networks or VPNs, preventing exposure to the public internet. 2. Implement network segmentation to isolate vulnerable routers from critical systems and sensitive data, reducing the blast radius of a potential DoS attack. 3. Monitor network traffic for unusual or malformed requests targeting the serviceName parameter or related router services, using intrusion detection/prevention systems (IDS/IPS). 4. Disable any unnecessary services or remote management features on the router to minimize the attack surface. 5. Regularly check for firmware updates from Tenda and apply patches promptly once available. 6. Consider replacing vulnerable devices with models from vendors with stronger security track records if immediate patching is not feasible. 7. Educate IT staff and end users about the risks and signs of router compromise or instability to enable rapid response. 8. Employ rate limiting or firewall rules to block suspicious traffic patterns that could exploit this vulnerability.

Description

CVE-2025-70747 is a high-severity stack overflow vulnerability found in the Tenda AX-1806 router, specifically in the serviceName parameter of the sub_65A28 function. Exploitation allows remote attackers to cause a denial of service (DoS) without requiring authentication or user interaction. The vulnerability has a CVSS score of 7.5, indicating significant impact on availability but no direct impact on confidentiality or integrity. No known exploits are currently in the wild, and no patches have been published yet. European organizations using Tenda AX-1806 routers could face network disruptions if targeted. Mitigation involves network segmentation, restricting access to router management interfaces, and monitoring for anomalous traffic. Countries with higher adoption of Tenda consumer networking equipment, such as Germany, France, and Italy, are more likely to be affected. Given the ease of exploitation and potential for service disruption, this vulnerability demands prompt attention to prevent denial of service attacks.

Impact

For European organizations, this vulnerability poses a significant risk to network availability, particularly for small businesses and home offices relying on Tenda AX-1806 routers. A successful attack could result in denial of service, causing network outages and loss of internet connectivity, which can disrupt business operations, remote work, and communications. Although the vulnerability does not compromise confidentiality or integrity, the loss of availability can have cascading effects on productivity and service delivery. Critical infrastructure or organizations with remote sites using these routers may experience operational interruptions. The lack of authentication requirement and ease of exploitation increase the threat level, especially if attackers scan for vulnerable devices exposed to the internet. This could also impact managed service providers supporting multiple clients with Tenda devices. The absence of patches means organizations must rely on network-level controls and monitoring to mitigate risk until a firmware update is available.

Summary

CVE-2025-70747 is a stack-based buffer overflow vulnerability identified in the Tenda AX-1806 router firmware version 1.0.0.1. The flaw resides in the handling of the serviceName parameter within the sub_65A28 function, where insufficient bounds checking allows an attacker to overflow the stack. This vulnerability can be triggered remotely by sending a specially crafted request to the affected router, leading to a denial of service (DoS) condition by crashing or destabilizing the device. The vulnerability does not require any privileges or user interaction, making it remotely exploitable over the network. The CVSS v3.1 base score of 7.5 reflects a high severity primarily due to the impact on availability (A:H), with no impact on confidentiality or integrity. The attack vector is network-based (AV:N), with low attack complexity (AC:L), and no privileges required (PR:N). Currently, there are no known exploits in the wild, and no official patches have been released, increasing the urgency for organizations to implement interim mitigations. The vulnerability is categorized under CWE-121 (Stack-based Buffer Overflow), a common and critical software weakness that can lead to crashes or code execution in other contexts, though this instance is limited to DoS. Given the widespread use of Tenda routers in consumer and small business environments, exploitation could disrupt internet connectivity and network availability.

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

github.com/0-fool/VulnbyCola/blob/main/Tenda/AX-1806/6/1.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 21 Jan 2026, 20:46 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats