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

New CVE Detected

CVE-2026-76070 – Pre-Auth Stack Buffer Overflow / Remote Code Execution – Netis NC63 Router (Firmwar

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

Summary

CVE-2026-76070 is a critical, pre-authentication stack-based buffer overflow in Netis NC63 wireless router firmware through version 3.0.0.3327. The flaw resides in the login handler of the netis.cgi binary, where an unsafe custom Base64 decoder fails to validate output length, allowing unauthenticated remote attackers to overwrite the stack and achieve remote code execution with root privileges. The vulnerability carries a severity score of 9.3–9.8 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: The device’s login handler decodes a Base64-encoded password using a custom decoder (FUN_00402bd4) that does not validate the size of its decoded output before writing it into a fixed 64-byte stack buffer.
  • Trigger conditions: An attacker submits an oversized Base64-encoded value in the password parameter to the login endpoint; the decode operation occurs before any comparison against the configured administrator password, so no valid credentials are needed.
  • Attack vector: Network-based, unauthenticated POST request to the CGI login endpoint (/cgi-bin/login.cgi, dispatched via /bin/netis.cgi) served by the Boa web server.
  • Impact: A sufficiently long decoded payload (roughly 136+ bytes) overwrites the saved return address on the stack, giving the attacker control of program execution. Because the Boa web server runs CGI processes as root, successful exploitation yields remote code execution with full root privileges. The binary lacks stack canaries, RELRO, PIE, and NX protections, which removes common barriers to exploitation.

Affected software

  • Netis NC63 Wireless AC1200 Router — firmware versions through NC63_V3.0.0.3327

Severity

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

Mitigation and recommended actions

  • Immediate: No official vendor patch has been confirmed as available. Check the Netis support site for firmware updates addressing this issue and apply them as soon as they are released.
  • If no patch is available:
    • Remove the router’s administration/login interface from direct internet exposure; restrict access to trusted internal networks or a management VPN only.
    • Place the device behind a firewall or reverse proxy that blocks or rate-limits requests to the CGI login endpoint.
    • Monitor for anomalous POST requests or crashes/restarts of the device’s web management service, which may indicate exploitation attempts.
    • Where feasible, replace or isolate affected NC63 units until a vendor fix is confirmed, given the device’s lack of standard binary exploit mitigations.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Named response header (Server): netis
  • Page title: Shock&Innovation!! netis setup, netis ... Router, netis 광대역 라우터 관리 패널

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