Security readout for executives and security teams
Plain-English summary
Comfast CF-N1-S devices running firmware 2.6.0.1 reportedly contain a memory-safety flaw in a web-facing CGI component. A remote, unauthenticated request involving width or height parameters could crash the device or compromise its data and operations. The supplied sources do not identify a patch or confirm attacks in the wild.
Executive priority
Treat this as an immediate inventory and containment priority wherever CF-N1-S devices may be deployed. Prioritize internet-reachable or operationally important devices running 2.6.0.1. Critical technical severity supports rapid exposure reduction, while the absence of confirmed exploitation and patch information means teams should avoid overstating incident likelihood and actively seek vendor guidance.
Technical view
The reported stack-based buffer overflow occurs in get_para_from_uri within /cgi-bin/mbox-config while parsing width or height URI parameters. The CVSS 4.0 vector indicates network access, low complexity, no privileges, no user interaction, and high impacts across confidentiality, integrity, and availability. Only CF-N1-S version 2.6.0.1 is identified as affected.
Likely exposure
Exposure is most likely where CF-N1-S devices run firmware 2.6.0.1 and the affected CGI interface is reachable from the internet or another untrusted network. The bundle does not establish whether the endpoint is enabled by default, management-only, or commonly exposed. Other versions should not be presumed affected without vendor confirmation.
Exploitation context
Remote initiation is reported, and the CVSS vector describes favorable attack conditions. However, the CVE is not listed as KEV, and none of the supplied evidence confirms active exploitation. The related GitHub repository may warrant defensive review, but the bundle provides insufficient detail to characterize it as a working public exploit.
Researcher notes
The evidence identifies the vulnerable function, CGI path, parameters, weakness classes, and one affected firmware version. It does not provide vendor confirmation, patch details, default reachability, crash evidence, or verified exploitation status. CWE-119 and CWE-121 support the memory-corruption classification. Safe validation should emphasize inventory, configuration review, and telemetry rather than triggering the overflow.
Mitigation direction
- Restrict untrusted network access to affected devices and their web management interface.
- Isolate confirmed 2.6.0.1 devices on segmented networks pending vendor guidance.
- Apply vendor-approved fixed firmware when Comfast identifies one; the supplied sources name no patch.
- Monitor for unusual requests to /cgi-bin/mbox-config and unexpected device restarts.
- Replace or retire devices if no supported remediation becomes available and exposure cannot be reduced.
Validation and detection
- Identify all Comfast CF-N1-S devices and record their installed firmware versions.
- Confirm whether version 2.6.0.1 is present; do not assume other versions are affected.
- Determine whether /cgi-bin/mbox-config is reachable from internet or other untrusted networks.
- Review device, proxy, and security logs for malformed width or height requests and unexplained crashes.
- Check Comfast guidance for confirmed affected releases and a fixed firmware version.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-76008 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (4.0)
- Known Exploited
- No
- Published
Vector: 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/E:X
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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/E:X——VulDBCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:X/RL:X/RC:R3.96VulDBCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:X/RL:X/RC:R3.96VulDBAV:N/AC:L/Au:N/C:C/I:C/A:C/E:ND/RL:ND/RC:UR1010VulDBVulnerability scoring details
Base CVSS 4.0 score
10CriticalVector: 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/E:X
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:X/RL:X/RC:R
Base CVSS 3.0 score
10CriticalVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:X/RL:X/RC:R
Base CVSS 2.0 score
10CriticalVector: AV:N/AC:L/Au:N/C:C/I:C/A:C/E:ND/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-391922 | Comfast CF-N1-S URI Parameter Parsing mbox-config get_para_from_uri stack-based overflowCVE reference, VulDB · vdb-entry, technical-description
- VDB-391922 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-76008 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #878007 | Comfast CF-N1-S V2.6.0.1 Stack-based Buffer OverflowCVE reference, VulDB · third-party-advisory
- https://github.com/1ChaoRen1/IOT_3CVE reference, VulDB · related
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.