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

New CVE Detected

CVE-2026-82542 – Unauthenticated Buffer Overflow (RCE/DoS) – Tenda HG10 Firmware 300001138 (Boa Web

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

Summary

CVE-2026-82542 is a critical buffer overflow vulnerability in the Boa web server component embedded in Tenda HG10 firmware (version 300001138). The flaw resides in the formIPv6Routing handler, where the destNet request parameter is copied into a fixed-size buffer without proper length validation, leading to memory corruption. The issue is remotely exploitable without authentication and carries a maximum CVSS v3.1 score of 10.0.

Technical details

  • Root cause: The formIPv6Routing function in the device’s Boa-hosted web management interface fails to validate or bound the length of the destNet argument before copying it into a stack buffer.
  • Trigger conditions: An attacker sends a crafted HTTP request to the /boaform/formIPv6Routing endpoint with an oversized destNet value.
  • Attack vector: Network — no authentication or user interaction is required to reach the vulnerable handler.
  • Impact: Memory corruption that can crash the Boa web server process and potentially allow arbitrary code execution on the device, resulting in full compromise of confidentiality, integrity, and availability.

Affected software

  • Tenda HG10 firmware version 300001138 (Boa Web Server component)

Severity

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

Mitigation and recommended actions

  • Immediate: No vendor patch is referenced in the public record for this CVE as of publication. Check Tenda’s official support channels for a firmware update addressing this issue before applying any fix.
  • If no patch is available:
    • Do not expose the HG10’s web management interface (Boa server) to the internet; restrict access to trusted LAN/management networks only.
    • Place management interfaces behind a VPN or firewall ACL that blocks inbound access to the device’s HTTP management port from untrusted networks.
    • Monitor for unusual POST requests to IPv6 routing configuration endpoints and for unexpected device reboots or crashes, which may indicate exploitation attempts.
    • Where possible, disable remote/WAN management on the device.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge