VulnerabilityPublished 23 Oct 2026Updated 28 Oct 2026

CVE-2026-115485: open-iscsi

Affects open-iscsiSource GCVE Database

Authoritative record:CVE-2026-115485· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium.

Data as of 28 Oct 2026, 22:31 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10open-iscsi`pkg:deb/ubuntu/open-iscsi?arch=source&distro=stonking`Other threats	Affected 2.1.11-3ubuntu3 – 2.1.11-5ubuntu6 5 affected builds	Fixed in–
Ubuntu 26.04 LTSopen-iscsi`pkg:deb/ubuntu/open-iscsi?arch=source&distro=resolute`Other threats	Affected 2.1.11-1ubuntu3 – 2.1.11-3ubuntu3.1 5 affected builds	Fixed in–
Ubuntu 24.04 LTSopen-iscsi`pkg:deb/ubuntu/open-iscsi?arch=source&distro=noble`Other threats	Affected 2.1.8-1ubuntu2 – 2.1.9-3ubuntu5.5 10 affected builds	Fixed in–
Ubuntu 22.04 LTSopen-iscsi`pkg:deb/ubuntu/open-iscsi?arch=source&distro=jammy`Other threats	Affected 2.1.4-0ubuntu1 – 2.1.5-1ubuntu1.3 7 affected builds	Fixed in–
Ubuntu 20.04 LTSopen-iscsi`pkg:deb/ubuntu/open-iscsi?arch=source&distro=focal`Other threats	Affected 2.0.874-7.1ubuntu3 – 2.0.874-7.1ubuntu6.5 8 affected builds	Fixed in–
Ubuntu Pro 18.04 LTSopen-iscsi`pkg:deb/ubuntu/open-iscsi?arch=source&distro=esm-infra/bionic`Other threats	Affected 2.0.874-4ubuntu3 – 2.0.874-5ubuntu2.11+esm1 15 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A flaw was found in the iscsiuio component of open-iscsi. The DHCPv6 option parser calls strlen() on raw network data without ensuring a NUL terminator is present, causing it to read past the buffer into heap memory. This can result in a daemon crash, a 1-byte heap overwrite, or corruption of the iSCSI initiator name. An attacker on the same network segment can trigger this by sending a crafted DHCPv6 Advertise message.

References

Community reviews

Loading reviews…