CVE-2025-70646
Memory Safety in Tenda Ax1803 Firmware 1.0.0.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2025-70646 is a high-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Tenda Ax1803 Firmware. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 24th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-70646 is a stack overflow vulnerability (CWE-121) in the security parameter of the sub_72290 function within Tenda AX1803 firmware version v1.0.0.1. This flaw enables attackers to trigger a Denial of Service (DoS) condition through a specially crafted network request. The vulnerability was publicly disclosed on January 21, 2026, and carries a CVSS v3.1 base score of 7.5, reflecting its high severity due to the potential for remote disruption without authentication.
The attack scenario is straightforward and highly accessible: unauthenticated attackers with network access to the affected device (AV:N/AC:L/PR:N/UI:N) can send a malicious request to the vulnerable function, causing a stack overflow that crashes the device and disrupts service availability (A:H). No user interaction or privileges are required, making it suitable for remote exploitation by any adversary on the same network or exposed to the internet. Successful exploitation results solely in DoS, with no impact on confidentiality or integrity (C:N/I:N).
Mitigation details and further technical analysis are provided in the referenced advisory at https://github.com/0-fool/VulnbyCola/blob/main/Tenda/AX-1803/5/1.md. Security practitioners should consult this source for reproduction steps, patch information if available, and recommended remediation actions, such as firmware updates or network segmentation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3656
Vulnerability Data
Tenda AX1803 v1.0.0.1 was discovered to contain a stack overflow in the security parameter of the sub_72290 function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted request.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can discover stack-buffer overflows before deployment.
Input validation directly stops untrusted data from exceeding stack buffer bounds.
Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.
Secure-engineering principles include bounds-checked coding and safe buffer handling that avoid introducing the flaw.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly prevent introduction of stack buffer overflows.
Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.
Patching eliminates known instances of the weakness after discovery.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing (fuzzing, static analysis) detects stack overflows before release.
Secure SDLC mandates buffer-safety practices that directly prevent stack overflows.
Application security requirements can specify buffer-size and input-validation rules.
Secure architecture principles include memory-safety and least-privilege stack usage.
Secure coding standards explicitly forbid unsafe buffer handling that causes CWE-121.
Change-management gates can enforce security reviews that catch buffer issues.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. prevents CWE-121
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-121