# CVE-2026-55995: Double-free in the iSNS attribute decoder in open-iscsi > An unauthenticated man-in-the-middle attacker can trigger a double-free in open-iscsi, causing a denial of service. - **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 29 Jul 2026 - **Updated:** 29 Jul 2026 - **Also known as:** ALSA-2026:53846, ALSA-2026:53847, ALSA-2026:53848, AZL-94434, CLSA-2026-1787739969, CLSA-2026-1787740913, DEBIAN-CVE-2026-55995, GHSA-93fw-mwmg-2g5m, MGASA-2026-0534, OESA-2026-3427, RHSA-2026:53846, RHSA-2026:53847, RHSA-2026:53848, RHSA-2026:59996, RHSA-2026:59999, RHSA-2026:60005, RHSA-2026:60006, RHSA-2026:60333, RHSA-2026:60385, RHSA-2026:61249, RLSA-2026:53846, RLSA-2026:53847, RLSA-2026:53848, UBUNTU-CVE-2026-55995, USN-8807-1, openSUSE-SU-2026:11456-1 ## What is CVE-2026-55995? CVE-2026-55995 is a high-severity use after free vulnerability in open-iscsi, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A Double Free vulnerability in open-iscsi allows an unauthenticated MITM attacker to cause DoS. This issue affects open-iscsi: from ? through 56718d4e9d1a4f51c30697b5c0534144bb41c9bb. Weakness: CWE-415 (Double Free) ## Which versions are affected by CVE-2026-55995? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `isns-utils` | AlmaLinux:10 | All versions | 0.103-1.el10_2.1 | | `isns-utils-libs` | AlmaLinux:10 | All versions | 0.103-1.el10_2.1 | | `isns-utils` | AlmaLinux:8 | All versions | 0.99-1.el8_10.1 | | `isns-utils-devel` | AlmaLinux:8 | All versions | 0.99-1.el8_10.1 | | `isns-utils-libs` | AlmaLinux:8 | All versions | 0.99-1.el8_10.1 | | `isns-utils` | AlmaLinux:9 | All versions | 0.101-4.el9_8.1 | | `isns-utils-libs` | AlmaLinux:9 | All versions | 0.101-4.el9_8.1 | | `isns-utils` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.103-1.el10_2.1 | | `isns-utils-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.103-1.el10_2.1 | | `isns-utils-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.103-1.el10_2.1 | | `isns-utils-libs` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.103-1.el10_2.1 | | `isns-utils-libs-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.103-1.el10_2.1 | | `isns-utils` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.99-1.el8_10.1 | | `isns-utils-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.99-1.el8_10.1 | | `isns-utils-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.99-1.el8_10.1 | | `isns-utils-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.99-1.el8_10.1 | | `isns-utils-libs` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.99-1.el8_10.1 | | `isns-utils-libs-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:0.99-1.el8_10.1 | | `isns-utils` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.101-4.el9_8.1 | | `isns-utils-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.101-4.el9_8.1 | | `isns-utils-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.101-4.el9_8.1 | | `isns-utils-libs` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.101-4.el9_8.1 | | `isns-utils-libs-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.101-4.el9_8.1 | | `isns-utils` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.103-1.el10_0.1 | | `isns-utils-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.103-1.el10_0.1 | | `isns-utils-debugsource` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.103-1.el10_0.1 | | `isns-utils-libs` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.103-1.el10_0.1 | | `isns-utils-libs-debuginfo` | Red Hat:enterprise_linux_eus:10.0 | All versions | 0:0.103-1.el10_0.1 | | `isns-utils` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:0.99-1.el8_4.1 | | `isns-utils-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:0.99-1.el8_4.1 | | `isns-utils-debugsource` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:0.99-1.el8_4.1 | | `isns-utils-devel` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:0.99-1.el8_4.1 | | `isns-utils-libs` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:0.99-1.el8_4.1 | | `isns-utils-libs-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:0.99-1.el8_4.1 | | `isns-utils` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:0.99-1.el8_6.1 | | `isns-utils-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:0.99-1.el8_6.1 | | `isns-utils-debugsource` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:0.99-1.el8_6.1 | | `isns-utils-devel` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:0.99-1.el8_6.1 | | `isns-utils-libs` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:0.99-1.el8_6.1 | | `isns-utils-libs-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:0.99-1.el8_6.1 | ## How do I fix CVE-2026-55995? Apply the vendor's patch. ## Is CVE-2026-55995 being exploited? There is no known exploitation of CVE-2026-55995 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-55995 and fix it if it is affected. What it is: CVE-2026-55995 is a high-severity use after free vulnerability in open-iscsi, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-55995 in the wild and no public exploit code. Affected product: open-iscsi. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-55995/ (Markdown: https://insights.sbomify.com/CVE-2026-55995/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55995 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55995 - OSV: https://osv.dev/vulnerability/CVE-2026-55995 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-55995/ Summaries are generated and may contain mistakes; the official description above is the record.