# CVE-2026-115486: Open-iscsi: open-iscsi: ipv6 neighbor discovery missing option length validation in iscsiuio allows arp table poisoning


- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-111392, DEBIAN-CVE-2026-115486, GHSA-9f4r-jjqf-4v98, UBUNTU-CVE-2026-115486

## What is CVE-2026-115486?

CVE-2026-115486 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 23 Oct 2026. 

### Official description

A flaw was found in the iscsiuio component of open-iscsi. The IPv6 Neighbor Discovery handler accesses link-layer address options at a fixed offset without verifying the packet contains them. Additionally, the ARP table is updated unconditionally with attacker-controlled addresses from the packet headers. An attacker on the same network segment can send a minimal Neighbor Advertisement to poison the ARP table and redirect network traffic.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-115486?


## How do I fix CVE-2026-115486?

No fix has been published for CVE-2026-115486 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115486 being exploited?

There is no known exploitation of CVE-2026-115486 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115486 and fix it if it is affected.

What it is: CVE-2026-115486 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115486 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-115486/ (Markdown: https://insights.sbomify.com/CVE-2026-115486/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115486
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115486
- OSV: https://osv.dev/vulnerability/CVE-2026-115486

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115486/
Summaries are generated and may contain mistakes; the official description above is the record.