LiveActive security incident?Get immediate response
CVE Record

CVE-2022-26988: TP-Link TL-WDR7660 2.0.30, Mercury D196G 20200109_2.0.4, and Fast FAC1900R 20190827_2.0.2 routers have a st...

TP-Link TL-WDR7660 2.0.30, Mercury D196G 20200109_2.0.4, and Fast FAC1900R 20190827_2.0.2 routers have a stack overflow issue in `MntAte` function. Local users could get remote code execution.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a stack overflow in specific TP-Link, Mercury, and Fast router firmware. The reported impact is remote code execution by local users, meaning risk depends heavily on who can access the affected router locally. The public bundle does not provide a CVSS score, vendor fix, or confirmed exploitation.

Executive priority

Prioritize verification where these routers support business-critical, shared, or sensitive networks. This is not source-confirmed as actively exploited, but router RCE can create meaningful network compromise risk if affected devices remain accessible.

Technical view

CVE-2022-26988 concerns the `MntAte` function in TP-Link TL-WDR7660 2.0.30, Mercury D196G 20200109_2.0.4, and Fast FAC1900R 20190827_2.0.2. The issue is described as stack overflow leading to remote code execution for local users. CWE, CVSS, exploit maturity, and remediation details are not supplied.

Likely exposure

Exposure appears limited to the named router models and firmware versions in the CVE description. The provided structured affected-product fields are incomplete, and the sources do not establish internet-facing exploitability.

Exploitation context

The bundle says local users could achieve remote code execution, but it does not define authentication requirements, attack surface, prerequisites, or active exploitation. CISA KEV status is false in the provided data.

Researcher notes

Evidence is sparse: no CVSS, CWE, CPEs, patch statement, or exploit-status details are provided. The phrase “local users could get remote code execution” is ambiguous and should not be expanded beyond the cited CVE text.

Mitigation direction

  • Inventory the named router models and firmware versions.
  • Check vendor guidance for firmware updates or replacement advice.
  • Restrict local access to router management and services.
  • Segment untrusted users away from router administration paths.
  • Replace unsupported affected devices if no fix is available.

Validation and detection

  • Confirm router model and firmware version from device management records.
  • Compare findings against the three versions named in the CVE description.
  • Review whether untrusted local users can reach router services.
  • Check vendor advisories before declaring remediation complete.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-26988 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.