Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-105285 – Critical Unauthenticated RCE (Stack-Based Buffer Overflow) – TOTOLINK A3002MU 1.0.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-105285 is a critical stack-based buffer overflow in the QoS Rule Handler of TOTOLINK A3002MU routers running firmware 1.0.0-B20230403.1455. The flaw resides in the /boafrm/formIpQoS endpoint and can be triggered remotely over the network with no authentication, allowing an attacker to crash the device’s management interface or potentially achieve arbitrary code execution as root. The issue has been assigned a maximum CVSS v3.1 base score of 10.0.

Technical details

  • Root cause: The formIpQoS handler copies the comment and entry_name parameters into a fixed 188-byte stack buffer using unbounded strcpy() calls, with no length validation on attacker-supplied input.
  • Trigger conditions: A POST request to /boafrm/formIpQoS with the addQos field set to a non-empty value and an oversized comment or entry_name value overflows the buffer.
  • Attack vector: Network-based, unauthenticated, requiring only a single HTTP request to the device’s exposed web management interface. The saved return address is located roughly 504 bytes above the buffer start, so a payload of around 508 bytes or more can overwrite it.
  • Impact: Denial of service (crash of the web management service) and potential remote code execution in the context of the web server process, which runs as root on the device, due to the absence of stack canaries and ASLR combined with a fixed binary load address.

Affected software

  • TOTOLINK A3002MU, firmware version 1.0.0-B20230403.1455

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No vendor patch has been identified at time of publication. Check the TOTOLINK support site for a firmware update addressing this issue and apply it as soon as it becomes available.
  • If no patch is available:
    • Restrict access to the router’s web management interface (/boafrm/* endpoints) to trusted internal networks only; do not expose it to the internet.
    • Disable remote/WAN administration on the device if enabled.
    • Place the device behind a firewall or VPN to limit exposure to the QoS configuration interface.
    • Monitor for unexpected POST requests to /boafrm/formIpQoS as a potential indicator of exploitation attempts.
    • Consider replacing or isolating end-of-life TOTOLINK devices that do not receive further firmware updates.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge