mz-automation libiec61850 up to 1.6.1 Report Sending Path reporting.c Reporting_RCBWriteAccessHandler free of memory not on the heap
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 1.26 |
Summary
A vulnerability was found in mz-automation libiec61850 up to 1.6.1. It has been classified as problematic. This issue affects the function Reporting_RCBWriteAccessHandler of the file src/iec61850/server/mms_mapping/reporting.c of the component Report Sending Path Handler. This manipulation causes free of memory not on the heap.
This vulnerability is handled as CVE-2026-18582. The attack can be initiated remotely. Additionally, an exploit exists.
Upgrading the affected component is recommended.
The vendor was contacted early about this disclosure.
Details
A vulnerability has been found in mz-automation libiec61850 up to 1.6.1 and classified as problematic. Affected by this vulnerability is the function Reporting_RCBWriteAccessHandler of the file src/iec61850/server/mms_mapping/reporting.c of the component Report Sending Path Handler. The manipulation with an unknown input leads to a free of memory not on the heap vulnerability. The CWE definition for the vulnerability is CWE-590. The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc(). As an impact it is known to affect availability.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-18582. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure.
Upgrading to version 1.6.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 5b2a69f44256b8548927d8afdd7ac5f5381abe1e is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Free of memory not on the heapCWE: CWE-590
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: libiec61850 1.6.2
Patch: 5b2a69f44256b8548927d8afdd7ac5f5381abe1e
Timeline
08/02/2026 Advisory disclosed08/02/2026 VulDB entry created
08/02/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-7qg8-hm25-rv5v
Status: Confirmed
CVE: CVE-2026-18582 (🔒)
GCVE (CVE): GCVE-0-2026-18582
GCVE (VulDB): GCVE-100-385411
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/02/2026 21:19Changes: 08/02/2026 21:19 (65)
Complete: 🔍
Submitter: Carnegie
Cache ID: 216::103
Submit
Accepted
- Submit #844920: MZ Automation GmbH libiec61850 1.6.1 Memory Corruption (by Carnegie)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.