Skip to main content

Comfast CF-N1-S CVE-2026-76008

| EUVDEUVD-2026-62224 CRITICAL
Stack-based Buffer Overflow (CWE-121)
2026-08-19 VulDB GHSA-m8hp-gppg-6x6v
10.0
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach device web interface
  2. Delivery
    Send crafted request to /cgi-bin/mbox-config
  3. Exploit
    Overflow stack via oversized width/height
  4. Execution
    Overwrite return address in get_para_from_uri
  5. Impact
    Execute arbitrary code / crash device

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the Comfast CF-N1-S HTTP management service and the ability to send a request to the /cgi-bin/mbox-config CGI with attacker-controlled width or height URI parameters - no credentials, session, or user interaction are needed per the CVSS 4.0 vector (PR:N/UI:N/AT:N). The concrete prerequisite is that the mbox-config endpoint and its get_para_from_uri parsing path are exposed to the attacker's network position; the primary limiting factor is therefore management-interface exposure: if the web UI is bound only to the LAN, remote internet exploitation is prevented, and only firmware 2.6.0.1 is confirmed affected.

Impact

The signals are largely aligned toward high urgency: the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) describes a trivially reachable, unauthenticated network attack, and the vendor-scored 10.0 reflects full compromise of confidentiality, integrity, and availability. Because the affected asset is network-edge infrastructure that is often internet-exposed, even a mid-sized municipal IT team in inowroclaw should treat this as urgent and hunt for exposed CF-N1-S management interfaces. That said, several tempering factors exist: no EPSS probability was supplied in the input, the CVE is not in CISA KEV (no confirmed active exploitation), and no packaged exploit is confirmed - the GitHub reference may contain a proof-of-concept but its maturity is unverified. The realistic caveat is exposure-dependent: if the mbox-config CGI is only reachable on the LAN, the AV:N rating overstates real-world reach, so verify whether the management interface is WAN-accessible before ranking this above other critical items.

Exploit ScenarioDerived

An attacker who can reach the device's web management interface sends a single crafted HTTP request to /cgi-bin/mbox-config with an over-long width (or height) parameter, overflowing the stack buffer in get_para_from_uri. With no authentication or user interaction required, this either crashes the CGI/device or, on the unprotected embedded target, redirects execution to attacker-supplied shellcode for remote code execution. The referenced GitHub repository may provide a working proof-of-concept, lowering the barrier to weaponization.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 19, 2026

Remote unauthenticated stack-based buffer overflow in the Comfast CF-N1-S wireless device (firmware 2.6.0.1) lets attackers corrupt memory by supplying oversized width/height values to the get_para_from_uri routine of the /cgi-bin/mbox-config endpoint. Because the flaw is reachable over the network with no authentication or user interaction (CVSS 4.0 base 10.0), a successful write can crash the device or achieve arbitrary code execution on the embedded firmware. It is not listed in CISA KEV and no productized exploit is confirmed, though a VulDB-referenced GitHub repository (1ChaoRen1/IOT_3) appears to document the finding.

RemediationAI

No vendor-released patch identified at time of analysis, and no fixed firmware version is cited in the source data, so remediation must rely on compensating controls. Primarily, remove the device management/HTTP interface from any untrusted or WAN-facing network and restrict access to the /cgi-bin/mbox-config endpoint to a trusted management VLAN or jump host via firewall ACLs - this blocks the remote vector at the cost of requiring on-network or VPN access for administration. Where feasible, place the device behind a reverse proxy or WAF that enforces length limits on the width and height URI parameters to reject oversized values, accepting the risk that this does not fix the underlying overflow. Monitor the vendor (Comfast) and the VulDB entry https://vuldb.com/cve/CVE-2026-76008 for a patched firmware release and apply it once published; if the device is end-of-life or exposed and unpatched, plan replacement. Do not deploy the affected firmware on internet-reachable segments.

Affected VersionsENISA

CF-N1-S 2.6.0.1

Affected Packages

euvd cf_n1_s no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the URI parameter parser (get_para_from_uri) inside the mbox-config CGI handler of the Comfast CF-N1-S, a small-form-factor CPE/wireless access device running Linux-based embedded firmware. CWE-121 (stack-based buffer overflow) is the root-cause class: the handler copies the attacker-controlled width and height query-string parameters into a fixed-size stack buffer without validating their length, allowing the saved return address and adjacent stack frame to be overwritten. On typical MIPS/ARM embedded targets with weak or absent stack protections (no stack canaries, RWX pages, no ASLR), such overflows in a CGI process frequently translate directly into remote code execution. The single affected CPE is cpe:2.3:a:comfast:cf-n1-s:*:*:*:*:*:*:*:* covering CF-N1-S 2.6.0.1.

Know when Cf N1 S gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 10.0 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
vuln.today AI 9.8 CRITICAL

Unauthenticated network request to the CGI with no user interaction gives AV:N/AC:L/PR:N/UI:N; memory-corruption RCE on the device yields C:H/I:H/A:H with scope unchanged.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

A flaw has been found in Comfast CF-N1-S 2.6.0.1. This affects the function get_para_from_uri of the file /cgi-bin/mbox-config of the component URI Parameter Parsing. This manipulation of the argument width/height causes stack-based buffer overflow. The attack can be initiated remotely.

Executive ViewAI

Why It Matters

The Comfast CF-N1-S wireless device (firmware 2.6.0.1) contains a critical remote code execution vulnerability accessible without authentication or user interaction, enabling attackers to execute arbitrary code and fully compromise device firmware. Organizations deploying this hardware face immediate risk of network access compromise and operational disruption.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: air-gap affected devices from production networks, implement network segmentation using a dedicated VLAN with ingress filtering to deny access to the /cgi-bin/mbox-config endpoint, disable remote management features if available, monitor Comfast security advisories and VulDB for patch releases, and maintain security logs for forensic review. Device replacement remains the primary remediation objective.

Threat Intelligence Overview

EPSS Score
0.6%
Top 55% exploitable
Prevalence
Low
niche Comfast consumer/SMB wireless device, limited enterprise footprint
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

51
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy