CVE Intelligence
Skip to main content
criticalMemory Corruption

CVE-2026-93738

CVE-2026-93738 — Totolink A3002MU formSchedule buffer overflow

A vulnerability was found in Totolink A3002MU Hh-B20211125.1046. This affects the function formSchedule of the file /boafrm/formSchedule. Performing a manipulation of the argument webpage results in buffer overflow. The attack is possible to be carried out remotely. The exploit has been made public and could be used.

Published Updated Sources: NVD, Totolink (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

ahead of 0% of scored CVEs

Affects

Totolink

A3002MU

CVSS base

9.9

critical · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade A3002MU to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
TotolinkA3002MUHh-B20211125.1046Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
9.9CVSS 3.1critical3.16NVD, GHSA
9CVSS 2.0high810vuldb.com (CNA)
9.4CVSS 4.0critical——Totolink (CNA)
9.9CVSS 3.1critical——Totolink (CNA)
9.9CVSS 3.0critical——Totolink (CNA)
9CVSS 2.0critical——Totolink (CNA)

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • Modify Memory
  • Execute Unauthorized Code or Commands
  • DoS: Crash, Exit, or Restart
  • DoS: Resource Consumption (CPU)

Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

  • Execute Unauthorized Code or Commands
  • Modify Memory
  • Read Memory
  • DoS: Crash, Exit, or Restart

Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

Weakness & attack patterns

  • CWE-120Classic Buffer Overflow
  • CWE-119Improper Restriction of Operations within a Memory Buffer

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-100 · Overflow BuffersCAPEC-8 · Buffer Overflow in an API CallCAPEC-92 · Forced Integer OverflowCAPEC-67 · String Format Overflow in syslog()CAPEC-24 · Filter Failure through Buffer OverflowCAPEC-10 · Buffer Overflow via Environment VariablesCAPEC-47 · Buffer Overflow via Parameter ExpansionCAPEC-44 · Overflow Binary Resource FileCAPEC-42 · MIME ConversionCAPEC-14 · Client-side Injection-induced Buffer OverflowCAPEC-9 · Buffer Overflow in Local Command-Line UtilitiesCAPEC-45 · Buffer Overflow via Symbolic Links

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /boafrm/formSchedule.
  • Prioritize edge telemetry for network-reachable A3002MU.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 9.9 (AV:N)

    Sep 18, 2026 · NVD

  3. Initial · CVE published

    Sep 18, 2026 · NVD

  4. Reported · Advisory disclosed

    Sep 18, 2026 · Totolink

  5. Reported · VulDB entry created

    Sep 18, 2026 · Totolink

  6. Reported · VulDB entry last update

    Sep 18, 2026 · Totolink

  7. Added · GHSA-cvqm-vq22-35jf published (high)

    Sep 18, 2026 · GitHub Security Advisory

  8. CVE published by MITRE.

    Sep 18, 2026 · SOCRadar CTI

References

8 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-93738 is Totolink A3002MU formSchedule buffer overflow, a critical vulnerability affecting A3002MU from Totolink. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-93738. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-93738. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.9 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.