Skip to main content

Mercusys AC12 V2 EUVDEUVD-2026-92785

| CVE-2026-78861 HIGH
Memory Allocation with Excessive Size Value (CWE-789)
2026-10-05 mitre GHSA-4jgr-x73g-p576
7.7
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

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

  1. Access
    Obtain local/firmware access to AC12 V2
  2. Delivery
    Extract hardcoded 512-bit RSA private key
  3. Exploit
    Forge trust or decrypt protected channel
  4. Execution
    Execute arbitrary code on device
  5. Impact
    Full device compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory allocation limits
Exploitation Conditions

Exploitation requires local access to the Mercusys AC12 V2 - either an on-device foothold (shell/serial/UART) or possession of the device firmware image from which the hardcoded 512-bit RSA private key can be extracted; the key is embedded in the firmware and shared across all units of this model. The primary LIMITING factors are: the local attack vector (AV:L) means no remote/internet exploitation and no automatable mass abuse (SSVC Automatable: no), and exploitation is constrained to this specific router model and firmware. No user interaction and no pre-existing authentication are required once local access is obtained (PR:N/UI:N). There is no confirmed active exploitation (not in CISA KEV), only a public advisory/POC.

Impact

This vulnerability presents a real but geographically/physically bounded risk rather than a mass-exploitation emergency. The CVSS vector (AV:L/AC:L/PR:N/UI:N) describes a local attack with low complexity and no required privileges, yielding high confidentiality and integrity impact but no availability impact (7.7, High). The local attack vector is the dominant limiting factor: an attacker needs local access to the device (shell, serial/UART, or extracted firmware) rather than remote network reach. SSVC corroborates this with Exploitation: poc, Automatable: no, and Technical Impact: total - meaning full compromise is possible but cannot be scaled in an automated internet-wide fashion. EPSS reinforces low urgency at 0.17% (6th percentile), consistent with a hardware/firmware flaw that is not remotely wormable. There is NO CISA KEV listing, so there is no confirmed active exploitation. A POC/advisory exists (SSVC=poc plus the ThreadPoolX GitBook advisory), so exploit knowledge is public. CONFLICT TO NOTE: the CWE is CWE-789 (Memory Allocation with Excessive Size Value), which does not match a 'hardcoded RSA private key' weakness - the correct mapping would be CWE-321 (Use of Hard-coded Cryptographic Key) or CWE-798; verify the CWE with the vendor/advisory. Also note the 512-bit RSA key length is cryptographically broken (factorable with modest resources), which makes the cryptographic-compromise aspect credible. Net: prioritize for affected device owners, but it is a high-CVSS, low-real-world-spread issue, not a widespread network emergency.

Exploit ScenarioDerived

An attacker with local access to a Mercusys AC12 V2 router (or a copy of its firmware) extracts the hardcoded 512-bit RSA private key, which is identical across all units of the model. Because 512-bit RSA is trivially factorable and the key is shared, the attacker can impersonate the device, decrypt or forge the protected communications/firmware-signing it secures, and leverage that trust to execute arbitrary code on the device. A public advisory/POC exists (ThreadPoolX GitBook), lowering the effort required, though the local attack vector prevents remote, automated mass exploitation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 06, 2026

Local code execution on the Mercusys AC12 V2 router is possible because a 512-bit RSA private key is hardcoded in the firmware image and shared across every unit of that model, so anyone who obtains the key - from the firmware binary or through an on-device shell, serial or UART foothold - can bypass the trust operation it protects and run arbitrary code on the device. Exploitation requires local access only, with no authentication and no user interaction (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, 7.7 High), while confidentiality and integrity impacts are rated High and availability is unaffected. There is no confirmed active exploitation (not in CISA KEV) and the SSVC assessment marks the issue non-automatable, but a public advisory/exploit exists and EPSS is low at 0.17% (6th percentile), placing this as a bounded, physical/adjacency-level risk rather than a mass-exploitation emergency.

RemediationAI

No vendor-released patch or fixed firmware version is identified at time of analysis, so the hardcoded 512-bit RSA key cannot currently be rotated by updating the device, and replacement or strict isolation should be considered the durable fix; check the Mercusys support site (http://mercusys.com) and the advisory write-up at https://threadpoolx.gitbook.io/docs/cve/mercusys-ac12-v2-security-advisory/hardcoded-private-key for any later firmware that removes or replaces the key. Until then, treat every AC12 V2 as having publicly known key material: disable WAN-side remote administration, port forwarding, UPnP/WPS, telnet/SSH and any debug or diagnostic service that authenticates with the embedded key, accepting the loss of remote-management convenience; physically secure the unit and lock down its serial/UART header and any exposed recovery interface, since the key is extractable with local access, at the cost of losing those recovery paths; place the router behind a segmented management network and restrict LAN/administrative access to trusted hosts, understanding this does not protect against a local foothold; and monitor for firmware re-flashing, unexpected configuration pushes, or anomalous update-package signatures that would indicate the key is being abused. Because the key is shared fleet-wide, remediating one device does not protect the others, and deployment-wide replacement should be planned for environments where the trust the key protects is security-relevant.

Affected VersionsENISA

n/a n/a

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

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

Technical ContextAI · show details

The defect is a cryptographic trust failure in the firmware of the Mercusys AC12 V2: a 512-bit RSA private key is embedded in the image and reused fleet-wide instead of being generated per device. RSA-512 is well below any modern minimum (2048-bit is the accepted floor) and is within practical factoring range for a determined attacker, so any signature verification, secure-boot check, or authenticated service that relies on this key can be forged by anyone holding it - which is effectively everyone with the firmware or one rooted unit. The supplied CPE strings are unpopulated placeholders (cpe:2.3:a:n/a:n/a), so CPE cannot be used to narrow the exact firmware builds; identification rests on the Mercusys AC12 V2 model designation in the description and EUVD record EUVD-2026-92785, whose affected-version field is also 'n/a'. The assigned CWE-789 (memory allocation with an excessive size value) does not describe this root cause class; the weakness maps far more naturally to CWE-321 (use of a hard-coded cryptographic key) or CWE-798 (use of hard-coded credentials), and that mismatch should be treated as a classification discrepancy while the operative facts - local vector, shared key material, unsigned/forgeable trust - remain as assessed.

Know when Mercusys 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 (mitre) PRIMARY 7.7 HIGH
AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 7.7 HIGH

Local firmware/device access only (AV:L); 512-bit key is trivially factorable and key is static (AC:L, PR:N); high confidentiality/integrity via key compromise and code execution, no availability loss (A:N).

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

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

3
CVSS changed
Oct 06, 2026 - 17:22 NVD
7.7 (None) 7.7 (HIGH)
CVE Published
Oct 05, 2026 - 00:00 cve.org
HIGH 7.7
CVE Published
Oct 05, 2026 - 00:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

An issue in Mercusys AC12 V2 allows a local attacker to execute arbitrary code via a hardcoded 512-bit RSA Private Key

Executive ViewAI

Why It Matters

Organizations using Mercusys AC12 V2 routers face a fleet-wide trust weakness: a shared secret embedded in every unit means a single locally obtained key can unlock arbitrary code execution on any of these devices. No vendor-released patch identified at time of analysis, and because exploitation requires only local, unauthenticated access, this is a targeted, location-dependent risk rather than a remote campaign, though successful compromise could undermine confidentiality and integrity of network traffic. Security leadership should care because these routers may sit at branch or remote sites where physical controls vary, and the shared key turns one local compromise into a reusable capability across the entire model fleet.

Business Impact: Medium
Compensating Controls

Enforce strict physical security for all AC12 V2 units, disable or physically block UART/serial interfaces where feasible, segment routers on isolated management VLANs, restrict administrative access to trusted personnel, monitor for unauthorized firmware changes, and plan replacement with a supported model. No vendor-released patch identified at time of analysis.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
single budget consumer Wi-Fi router model, limited per-model footprint
Data Quality
5 sources
Confidence: Medium

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 HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
Poc
System Exposure· derived
Small
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

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

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2022-26988 HIGH POC
7.8 May 10

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

CVE-2022-26987 HIGH POC
7.8 May 10

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

CVE-2025-56463 MEDIUM POC
6.8 Sep 26

Mercusys MW305R 3.30 and below is has a Transport Layer Security (TLS) certificate private key disclosure. Rated medium

CVE-2021-25810 MEDIUM POC
6.1 Apr 29

Cross site Scripting (XSS) vulnerability in MERCUSYS Mercury X18G 1.0.5 devices, via crafted values to the 'src_dport_st

CVE-2021-23242 MEDIUM POC
5.3 Jan 07

MERCUSYS Mercury X18G 1.0.5 devices allow Directory Traversal via ../ to the UPnP server, as demonstrated by the /../../

CVE-2021-23241 MEDIUM POC
5.3 Jan 07

MERCUSYS Mercury X18G 1.0.5 devices allow Directory Traversal via ../ in conjunction with a loginLess or login.htm URI (

CVE-2026-78860 HIGH
7.8 Oct 05

Plaintext storage of sensitive data on the Mercusys AC12 V2 router, compounded by the absence of any secure boot mechani

CVE-2021-25811 HIGH
7.5 Apr 29

MERCUSYS Mercury X18G 1.0.5 devices allow Denial of service via a crafted value to the POST listen_http_lan parameter. R

CVE-2026-78862 MEDIUM
6.8 Oct 05

Physical access to a Mercusys AC12 V2 router's printed circuit board lets an attacker take full control of the device: t

CVE-2026-12495 MEDIUM
5.3 Jul 27

Denial-of-service in the Mercusys MB115-4G router's web interface allows unauthenticated attackers to crash the administ

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