How severe is CVE-2025-0657?

CVE-2025-0657 has a CVSS 4.0 base score of 8.8, rated high severity.

Is CVE-2025-0657 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-0657?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-0657 have an EU (EUVD) identifier?

Yes. CVE-2025-0657 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-199779.

When was CVE-2025-0657 published?

CVE-2025-0657 was published on 2025-11-27 and last updated on 2026-06-17.

CVE-2025-0657

CVE-2025-0657 is a high-severity vulnerability with a CVSS 4.0 base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-129.

Key facts

Severity: High (CVSS 4.0 base score 8.8)
EPSS exploit prediction: 0% (21st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-199779
Weakness: CWE-129
Published: 2025-11-27
Last modified: 2026-06-17

Description

A weakness in Automated Logic and Carrier i-Vu Gen5 router on driver version drv_gen5_106-01-2380, allows malformed packets to be sent through BACnet MS/TP network causing the devices to enter a fault state. This fault state requires a manual power cycle to return the device to network visibility.

Frequently asked questions

What is CVE-2025-0657?: A weakness in Automated Logic and Carrier i-Vu Gen5 router on driver version drv_gen5_106-01-2380, allows malformed packets to be sent through BACnet MS/TP network causing the devices to enter a fault state. This fault state requires a manual power cycle to return the device to network visibility.
How severe is CVE-2025-0657?: CVE-2025-0657 has a CVSS 4.0 base score of 8.8, rated high severity.
Is CVE-2025-0657 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-0657?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-0657 have an EU (EUVD) identifier?: Yes. CVE-2025-0657 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-199779.
When was CVE-2025-0657 published?: CVE-2025-0657 was published on 2025-11-27 and last updated on 2026-06-17.

References

https://www.corporate.carrier.com/product-security/advisories-resources/

Other CWE-129 (Improper Validation of Array Index) vulnerabilities

CVE-2020-27485 — Critical (CVSS 9.9): Garmin Forerunner 235 before 8.20 is affected by: Array index error. The component is: ConnectIQ TVM. The attack vector…
CVE-2020-27483 — Critical (CVSS 9.9): Garmin Forerunner 235 before 8.20 is affected by: Array index error. The component is: ConnectIQ TVM. The attack vector…
CVE-2026-21413 — Critical (CVSS 9.8): A heap-based buffer overflow vulnerability exists in the lossless_jpeg_load_raw functionality of LibRaw Commit 0b56545…
CVE-2025-27034 — Critical (CVSS 9.8): Memory corruption while selecting the PLMN from SOR failed list.
CVE-2025-3357 — Critical (CVSS 9.8): IBM Tivoli Monitoring 6.3.0.7 through 6.3.0.7 Service Pack 19 could allow a remote attacker to execute arbitrary code…
CVE-2024-45569 — Critical (CVSS 9.8): Memory corruption while parsing the ML IE due to invalid frame content.

Browse all CWE-129 (Improper Validation of Array Index) vulnerabilities →