CVE-2025-46060
Memory Safety in Totolink N600R Firmware 4.3.0cu.7866_b2022506
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-46060 is a critical-severity Classic Buffer Overflow (CWE-120) vulnerability in Totolink N600R Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 45% of CVEs by exploit likelihood; 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-46060 is a buffer overflow vulnerability, tracked under CWE-120, that affects the TOTOLINK N600R router running firmware version 4.3.0cu.7866_B2022506. The flaw resides in the UPLOAD_FILENAME component and carries a CVSS 3.1 base score of 9.8, reflecting network-accessible, unauthenticated exploitation that can fully compromise confidentiality, integrity, and availability.
A remote attacker can supply a crafted upload filename to trigger the overflow and execute arbitrary code on the device without requiring credentials or user interaction. The attack is possible over the network with low complexity, enabling complete takeover of the affected router.
The provided references point to the vendor site and a public GitHub repository containing technical details, but no official patch or mitigation guidance is described in the available information. The associated EPSS score remains low, with a current value of 0.0211 and a peak of 0.0213, indicating limited observed exploitation interest to date.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18267
Vulnerability Data
Buffer Overflow vulnerability in TOTOLINK N600R v4.3.0cu.7866_B2022506 allows a remote attacker to execute arbitrary code via the UPLOAD_FILENAME component
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can find missing size checks before deployment.
Input validation directly enforces size checks before buffer copies.
Engineering principles require bounds checking and safe buffer handling in design.
Memory protection limits the impact of an overflow once it occurs.
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 enforce bounds checking and input validation that prevent classic buffer overflows.
Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.
Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.
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.
Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.
Security testing in development and acceptance can detect buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.
Secure development life cycle mandates processes that can include input validation and bounds checking to prevent buffer overflows.
Application security requirements can specify input-size validation and safe buffer handling to mitigate classic buffer overflows.
Secure system architecture and engineering principles promote defensive coding patterns that reduce the likelihood of unchecked buffer copies.