CVE-2026-36610
Deferred Deferred - Pending Action
Mercusys AC12G (EU) V1 Firmware Plaintext DDNS Credential Transmission

Publication date: 2026-06-03

Last updated on: 2026-06-03

Assigner: MITRE

Description
Mercusys AC12G (EU) V1 with firmware AC12G(EU)_V1_200909 transmits DDNS credentials over plaintext HTTP with only Base64 encoding. The firmware contains no TLS implementation, allowing man-in-the-middle interception of DDNS service credentials.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-03
Last Modified
2026-06-03
Generated
2026-06-24
AI Q&A
2026-06-03
EPSS Evaluated
2026-06-22
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
mercusys ac12g ac12g(eu)_v1_200909
mercusys ac12g ac12g(eu)_v1_210128
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-319 The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
CWE-523 Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2026-36610 affects the Mercusys AC12G (EU) V1 router with firmware AC12G(EU)_V1_200909. The vulnerability involves the transmission of Dynamic DNS (DDNS) credentials over plaintext HTTP, where the credentials are only encoded using Base64, which is easily reversible.

Because the firmware does not implement TLS or SSL, these credentials can be intercepted by anyone monitoring the network, such as ISPs, WiFi eavesdroppers, or man-in-the-middle attackers.

This means sensitive information like DDNS service credentials can be exposed during transmission to DDNS providers.

Impact Analysis

The vulnerability can lead to the exposure of your DDNS credentials to attackers who can intercept network traffic.

With these credentials, an attacker could potentially gain unauthorized access to your DDNS service, which might allow them to redirect your domain name services or disrupt your network connectivity.

This exposure increases the risk of man-in-the-middle attacks and compromises the confidentiality of your network communications.

Detection Guidance

This vulnerability can be detected by monitoring network traffic for DDNS credential transmissions over plaintext HTTP. Since the credentials are only Base64 encoded and not encrypted, capturing HTTP traffic to DDNS providers like DynDNS or No-IP can reveal sensitive information.

  • Use packet capture tools such as Wireshark or tcpdump to filter HTTP traffic on your network.
  • Example tcpdump command to capture HTTP traffic: tcpdump -i <interface> -A 'tcp port 80 and host <DDNS_provider_IP_or_hostname>'
  • Inspect captured HTTP packets for Base64 encoded strings in the DDNS credential fields, which can be decoded to verify if credentials are transmitted in plaintext.
Mitigation Strategies

Immediate mitigation steps include avoiding the use of the vulnerable Mercusys AC12G (EU) V1 firmware versions that transmit DDNS credentials without encryption.

Since the affected product is end-of-life with no planned fixes, the recommended action is to implement TLS for outbound connections or use DDNS providers that support HTTPS endpoints to protect credential transmission.

Alternatively, consider replacing the vulnerable device with a router that supports secure DDNS credential transmission over TLS/SSL.

Compliance Impact

The vulnerability involves transmitting DDNS credentials in plaintext over HTTP with only Base64 encoding, which is easily reversible. This cleartext transmission of sensitive information can lead to unauthorized interception of credentials by attackers.

Such insecure transmission of sensitive data likely violates common security requirements in standards and regulations like GDPR and HIPAA, which mandate protecting personal and sensitive information during transmission to prevent unauthorized access.

Because the firmware lacks TLS or SSL implementation, it fails to provide adequate protection for credentials in transit, potentially leading to non-compliance with these regulations' data protection and privacy requirements.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-36610. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart