CVE-2026-55995
open-iscsi double-free enables MITM remote DoS of iSCSI initiator
Is CVE-2026-55995 being exploited?
Not confirmed. CVE-2026-55995 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-55995?
CVE-2026-55995 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-55995?
Not known from our data. No patch reference has been recorded for CVE-2026-55995, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-55995 affect?
CVE-2026-55995 affects open-iscsi (affected commits up to 56718d4e9d1a4f51c30697b5c0534144bb41c9bb), Linux systems using open-iscsi iSCSI initiator. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55995?
Apply vendor/open-iscsi patch when released; isolate and encrypt iSCSI traffic to prevent MITM.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated MITM can trigger a double-free in open-iscsi, crashing the initiator and causing storage connectivity denial of service.
Patch when possible
- affected>= ? and <= 56718d4e9d1a4f51c30697b5c0534144bb41c9bb
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.