A vulnerability was found in Anviz CX7 and classified as problematic . The affected element is an unknown function of the component MQTT Handler . Executing a manipulation can lead to use of hard-coded cryptographic key . This vulnerability is tracked as CVE-2026-32324 . The attack can be launched remotely. No exploit exists.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358013 · CVE-2026-32324 · ICSA-26-106-03
ANVIZ CX7 MQTT HARD-CODED KEY
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
3.6 $0-$5k 3.49+
Summaryinfo
A vulnerability was found in Anviz CX7. It has been classified as problematic. The impacted element is an unknown function of the component MQTT Handler. The manipulation leads to hard-coded key. This vulnerability is listed as CVE-2026-32324. The attack may be initiated remotely. There is no available exploit.
Detailsinfo
A vulnerability, which was classified as problematic, has been found in Anviz CX7 (unknown version). This issue affects an unknown code block of the component MQTT Handler. The manipulation with an unknown input leads to a hard-coded key vulnerability. Using CWE to declare the problem leads to CWE-321. The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered. Impacted is confidentiality.
The advisory is shared at cisa.gov. The identification of this vulnerability is CVE-2026-32324. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Vendor
Anviz
Name
CX7
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 3.7
VulDB Meta Temp Score: 3.6
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
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: 🔍
Exploitinginfo
Class: Hard-coded key
CWE: CWE-321 / CWE-320
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
04/17/2026 Advisory disclosed
04/17/2026 +0 days VulDB entry created
04/17/2026 +0 days VulDB entry last update
Sourcesinfo
Advisory: icsa-26-106-03
Status: Not defined
CVE: CVE-2026-32324 (🔒)
GCVE (CVE): GCVE-0-2026-32324
GCVE (VulDB): GCVE-100-358013
Entryinfo
Created: 04/17/2026 06:51
Changes: 04/17/2026 06:51 (49)
Complete: 🔍
Cache ID: 99:1D8:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸