Mercusys AC12G POST Request SOAPAction uninitialized pointer
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 1.45 |
Summary
A vulnerability classified as very critical has been found in Mercusys AC12G. The impacted element is an unknown function of the component POST Request Handler. Performing a manipulation of the argument SOAPAction results in uninitialized pointer. This vulnerability is cataloged as CVE-2026-36611. The attack must originate from the local network. There is no exploit available.
Details
A vulnerability classified as very critical has been found in Mercusys AC12G (version now known). This affects some unknown processing of the component POST Request Handler. The manipulation of the argument SOAPAction with an unknown input leads to a uninitialized pointer vulnerability. CWE is classifying the issue as CWE-824. The product accesses or uses a pointer that has not been initialized. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Mercusys AC12G (EU) V1 with firmware AC12G(EU)_V1_200909 returns 128 bytes of uninitialized buffer when receiving POST requests without SOAPAction header on UPnP port 1900, exposing internal memory to unauthenticated adjacent network attackers.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-36611 since 04/06/2026. The exploitability is told to be easy. Access to the local network is required for this attack to succeed. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/03/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.5
VulDB Base Score: 8.8
VulDB Temp Score: 8.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Uninitialized pointerCWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/06/2026 CVE reserved06/03/2026 Advisory disclosed
06/03/2026 VulDB entry created
06/03/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2026-36611 (🔒)
GCVE (CVE): GCVE-0-2026-36611
GCVE (VulDB): GCVE-100-368199
Entry
Created: 06/03/2026 21:44Changes: 06/03/2026 21:44 (52)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.