VYPR
Unrated severityNVD Advisory· Published Jun 3, 2026

CVE-2026-36602

CVE-2026-36602

Description

Mercusys AC12G router firmware leaks kernel memory addresses via UPnP, aiding attackers on the adjacent network.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Mercusys AC12G router firmware leaks kernel memory addresses via UPnP, aiding attackers on the adjacent network.

Vulnerability

The Mercusys AC12G (EU) V1 router, specifically firmware versions AC12G(EU)_V1_200909 and AC12G(EU)_V1_210128, is vulnerable to kernel memory disclosure. The UPnP GetStatusInfo action on the WANIPConnection service, accessible via /ipc on port 1900, incorrectly returns a raw MIPS KSEG0 kernel memory address instead of the expected connection status string [1].

Exploitation

An unauthenticated attacker on the adjacent network can send a crafted UPnP request to the GetStatusInfo action. The router will respond with a raw kernel virtual address within the NewConnectionStatus field, effectively bypassing authentication as UPnP is typically accessible on the LAN without credentials [1].

Impact

Successful exploitation allows an attacker to obtain a raw MIPS KSEG0 kernel pointer. Since VxWorks, the operating system used, lacks ASLR, this leak provides a reliable map of the kernel's memory layout. This information significantly aids in the development of further exploits, potentially leading to code execution, especially given the absence of stack canaries and NX bit protection on VxWorks [1].

Mitigation

This vulnerability affects end-of-life products, and no fix is planned. The available references suggest that the pointer should be dereferenced before string formatting and that the printf format specifier should be corrected. However, no patched firmware version or workaround has been disclosed [1].

AI Insight generated on Jun 3, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1