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

New CVE Detected

CVE-2026-77946 – Remote Code Execution via Stack-Based Buffer Overflow – TRENDnet TEW-821DAP 2.2.01b

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

Summary

CVE-2026-77946 is a critical, unauthenticated stack-based buffer overflow vulnerability in the TRENDnet TEW-821DAP wireless access point running firmware 2.2.01b05. The flaw resides in the uci_safe_get function used by the NTP Timezone Configuration Handler (/cgi-bin/apply_time.cgi), and can be triggered remotely over the network without authentication. It carries the maximum CVSS v3.1 base score of 10.0 (Critical) and a public proof-of-concept exploit is available.

Technical details

  • Root cause: The uci_safe_get function reads user-controlled UCI configuration parameters and copies them into fixed-size stack buffers using an unbounded copy operation, without validating input length.
  • Trigger conditions: An attacker sends a crafted HTTP POST request to /cgi-bin/apply_time.cgi, supplying an oversized value in one of the parameters system.ntp.server, system.ntp.enable_server, cameo.time.time_zone, or cameo.cameo.syslog_server.
  • Attack vector: Network-based, no authentication or user interaction required, low attack complexity.
  • Impact: Overwriting the saved return address on the stack allows an attacker to redirect program execution, potentially achieving arbitrary code execution with root/service privileges on the device, and can otherwise crash the affected service (denial of service).

Affected software

  • TRENDnet TEW-821DAP, firmware version 2.2.01b05 (component: NTP Timezone Configuration Handler / /cgi-bin/apply_time.cgi)

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 official TRENDnet patch or firmware update addressing CVE-2026-77946 has been identified at this time. Check the TRENDnet support/downloads page for the TEW-821DAP for any newer firmware release and apply it as soon as it becomes available.
  • If no patch: Restrict access to the device’s management/configuration interface (/cgi-bin/apply_time.cgi and related CGI endpoints) to trusted internal networks only; do not expose the administrative interface directly to the internet. Place the device behind a firewall or VPN, disable remote/WAN administration if enabled, and monitor for anomalous POST requests to time/NTP configuration endpoints. Given the device is discontinued/end-of-life for related hardware revisions, evaluate replacing the access point with a currently supported model.

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