CVE-2026-50039

Deferred Deferred - Pending Action

BaseFortify

Publication date: 2026-07-23

Last updated on: 2026-07-30

Assigner: ICS-CERT

Description

The affected product is vulnerable to a stack-based buffer overflow, which may allow an attacker to cause a memory corruption via a Read Request.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-23

Last Modified

2026-07-30

Generated

2026-10-12

AI Q&A

2026-07-24

EPSS Evaluated

2026-10-11

NVD

CVE-2026-50039

Affected Vendors & Products

Vendor	Product	Version / Range
MZ	Automation	libIEC61850 1.0.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-121	A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Attack-Flow Graph

Executive Summary

This vulnerability is a stack-based buffer overflow in an unspecified product. It occurs when a Read Request is processed, potentially allowing an attacker to corrupt memory by writing beyond the intended buffer limits.

Detection Guidance

Detection of this stack-based buffer overflow vulnerability typically requires monitoring for abnormal memory access patterns or crashes in the affected application. Use system logs to check for segmentation faults or memory corruption errors. Network monitoring tools can detect unusual read request patterns that may exploit this issue.

Impact Analysis

An attacker could exploit this to cause memory corruption, leading to crashes, denial of service, or potentially arbitrary code execution. The high impact on availability (A:H in CVSS) suggests system disruption is likely.

Compliance Impact

The vulnerability is a stack-based buffer overflow that could lead to memory corruption via a Read Request. This type of vulnerability may impact compliance by potentially exposing sensitive data or disrupting system integrity, which are key concerns under standards like GDPR and HIPAA. However, specific compliance impacts are not detailed in the provided CVE data.

Mitigation Strategies

Immediate mitigation steps include applying vendor patches if available, isolating affected systems from the network, monitoring for unusual activity, and restricting network access to the vulnerable service.

Hi! I’m here to help you understand CVE-2026-50039. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70