# CVE-2026-105453: IBM Sterling Connect:Direct for Unix Improper Privilege Management

> A local attacker can gain elevated privileges in IBM Sterling Connect:Direct for Unix due to improper privilege management.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A: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:** No
- **Published:** 19 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-889c-pwpc-x9cq

## What is CVE-2026-105453?

CVE-2026-105453 is a high-severity vulnerability in IBM Sterling Connect Direct for Unix, published on 19 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Sterling Connect Direct for Unix 6.3.0.0 through 6.3.0.7 and 6.4.0.0 through 6.4.0.6 could allow a local attacker to gain elevated privileges due to improper privilege management.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-105453 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105453 is a high-severity vulnerability in IBM Sterling Connect Direct for Unix, published on 19 Oct 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-105453 in the wild and no public exploit code.

Affected product: IBM Sterling Connect Direct for Unix. 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-105453/ (Markdown: https://insights.sbomify.com/CVE-2026-105453/index.md)
```

## Sources

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

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