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

New CVE Detected

CVE-2026-94003 – Unauthenticated Remote Code Execution / Stack Buffer Overflow – Comfast CF-N1-S 2.6

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

Summary

CVE-2026-94003 is a critical, unauthenticated stack-based buffer overflow affecting the Comfast CF-N1-S wireless access point/router, firmware version 2.6.0.1. The flaw resides in the get_css_path_from_uri function used by the /cgi-bin/mbox-config endpoint of the device’s Web Management Interface, and can be triggered remotely over the network with no authentication or user interaction. The issue has been assigned a maximum CVSS v3.1 base score of 10.0 and a public proof-of-concept exploit is already available.

Technical details

  • Root cause: The get_css_path_from_uri function copies the portion of the request URI preceding the ? character into a fixed-size stack buffer without validating the input length against the buffer’s capacity. The copy loop only stops at a ? character or a string terminator, so an overlong path segment overflows adjacent stack memory.
  • Trigger condition: Sending an HTTP GET request to /cgi-bin/mbox-config/ with an excessively long path component before the query string (proof-of-concept exploits use a path of repeated characters, e.g. 100+ bytes) overflows the stack buffer.
  • Attack vector: Network-based (AV:N), low attack complexity, no privileges and no user interaction required — the endpoint is reachable without any login/session validation.
  • Impact: Overwriting stack data can crash the web management process (denial of service) and, depending on the target’s memory layout and lack of stack protections, may allow overwriting of a return address to achieve arbitrary code execution on the device. Exploitation has been confirmed via firmware emulation, demonstrating a reliable process crash.

Affected software

  • Comfast CF-N1-S — firmware version 2.6.0.1 (Web Management Interface / mbox-config component)

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-issued patched firmware version has been confirmed as of this writing. Check the Comfast support portal regularly for a firmware update addressing this issue and apply it as soon as it becomes available.
  • If no patch is available:
    • Do not expose the CF-N1-S web management interface (/cgi-bin/mbox-config) to the public internet or untrusted networks; restrict access to trusted management VLANs/IP ranges only.
    • Place the device’s management interface behind a VPN or firewall ACL that limits inbound access to authorized administrators.
    • Monitor for anomalous long-URI requests to /cgi-bin/mbox-config at the network perimeter (WAF/IPS) as an indicator of exploitation attempts.
    • Where feasible, replace or isolate affected devices until a fix is confirmed, given the maximum severity and public availability of exploit code.

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