Is CVE-2026-55995 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55995 being exploited in the wild.

How severe is CVE-2026-55995?

Informational severity, with a CVSS score of 8.7, published 29 July 2026.

Which products and versions are affected?

Open-iSCSI Project Open-Iscsi up to commit 56718d4e9d1a4f51c30697b5c0534144bb41c9bb; Open-iSCSI Project Open-Isns up to commit 56718d4e9d1a4f51c30697b5c0534144bb41c9bb.

Is there a fix for CVE-2026-55995?

A patch was published on 2026-07-29: Fix committed to open-isns repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55995 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-55995?

Check whether you run Open-iSCSI Project Open-Iscsi or Open-iSCSI Project Open-Isns at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55995: open-iscsi Double Free in open-isns attrs.c

CVE-2026-55995 · Severity: info · CVSS 8.7 · Published 2026-07-29

A vulnerability in the open-iscsi software suite could allow a remote attacker to crash the service, leading to a denial-of-service. This software is commonly used to connect Linux systems to network-based storage (SANs). An exploit would disrupt the connection between servers and their storage disks, potentially halting business operations and data access.

Technologies: Open-iSCSI Project Open-Iscsi. Vendors: Open-iSCSI Project.

Quick answers

Is CVE-2026-55995 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55995 being exploited in the wild.
How severe is CVE-2026-55995?: Informational severity, with a CVSS score of 8.7, published 29 July 2026.
Which products and versions are affected?: Open-iSCSI Project Open-Iscsi up to commit 56718d4e9d1a4f51c30697b5c0534144bb41c9bb; Open-iSCSI Project Open-Isns up to commit 56718d4e9d1a4f51c30697b5c0534144bb41c9bb.
Is there a fix for CVE-2026-55995?: A patch was published on 2026-07-29: Fix committed to open-isns repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55995 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-55995?: Check whether you run Open-iSCSI Project Open-Iscsi or Open-iSCSI Project Open-Isns at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A double-free vulnerability exists in the open-isns component of open-iscsi within the attrs.c file. The flaw is located in the error handling paths of isns_attr_type_string_decode and isns_attr_type_opaque_decode; when buf_get() fails, the allocated memory is freed but the pointer is not set to NULL, leading to a subsequent free of the same memory address. An unauthenticated attacker positioned as a Man-in-the-Middle (MITM) can trigger this condition to cause a crash (Denial of Service). The issue is addressed in commit 56718d4e9d1a4f51c30697b5c0534144bb41c9bb.

Affected products

open-iscsi open-iscsi up to commit 56718d4e9d1a4f51c30697b5c0534144bb41c9bb
open-iscsi open-isns up to commit 56718d4e9d1a4f51c30697b5c0534144bb41c9bb

Timeline

2026-07-29: disclosed
2026-07-29: advisory
2026-07-29: patched: Fix committed to open-isns repository

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.