CVE-2026-52134: Critical severity libiec61850 libiec61850 vulnerability

Published Jul 31, 2026

Updated

An issue in the parseGoosePayload() function (/goose/goosereceiver.c) of libiec61850 v1.6 allows attackers to bypass authentication via a captured GOOSE frame.

Affected Software

1 affected component

libiec61850 libiec61850=1.6

Event History

Jul 31, 2026

CVE Published

via MITRE·12:00 AM

Data Sourced

via MITRE·12:00 AM

Description

Data Sourced

via NVD·10:17 PM

DescriptionSeverityWeakness

Frequently Asked Questions

What is the severity of CVE-2026-52134?

CVE-2026-52134 has a critical severity rating of 9.8 based on the CVSS 3.1 metrics.

How do I fix CVE-2026-52134?

To fix CVE-2026-52134, update to the latest version of libiec61850 that addresses this vulnerability.

What impact does CVE-2026-52134 have on systems?

CVE-2026-52134 allows attackers to bypass authentication, potentially granting unauthorized access to sensitive system operations.

Who is affected by CVE-2026-52134?

Users of libiec61850 version 1.6 are primarily affected by CVE-2026-52134.

What software is involved in CVE-2026-52134?

CVE-2026-52134 involves the libiec61850 library, specifically in its implementation within the parseGoosePayload() function.

CVE-2026-52134: Critical severity libiec61850 libiec61850 vulnerability

Affected Software

Event History

Don't miss critical vulnerabilities

Frequently Asked Questions

What is the severity of CVE-2026-52134?

How do I fix CVE-2026-52134?

What impact does CVE-2026-52134 have on systems?

Who is affected by CVE-2026-52134?

What software is involved in CVE-2026-52134?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2026-52134?

How do I fix CVE-2026-52134?

What impact does CVE-2026-52134 have on systems?

Who is affected by CVE-2026-52134?

What software is involved in CVE-2026-52134?