# CVE-2026-44944: iscsiuio control-socket authentication bypass in open-iscsi

> Unprivileged local users can bypass authentication to access the iscsiuio control socket in open-iscsi, potentially escalating privileges.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** AZL-94431, DEBIAN-CVE-2026-44944, GHSA-jm64-8832-wmmq, UBUNTU-CVE-2026-44944

## What is CVE-2026-44944?

CVE-2026-44944 is a high-severity authentication bypass vulnerability in open-iscsi, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Incorrect Authorization vulnerability in open-iscsi allows unprivilidged local users to use the isscsiuio control socket.

This issue affects open-iscsi: from ? through 668ca1df9c9a1e9bdd5c999ae1d67c9c8909237e.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Apply the vendor's patch.

## Is CVE-2026-44944 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44944 is a high-severity authentication bypass vulnerability in open-iscsi, published on 29 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44944 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-44944/ (Markdown: https://insights.sbomify.com/CVE-2026-44944/index.md)
```

## Sources

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

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