CVE-2026-105453
published 2026-10-20CVE-2026-105453: 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…
PriorityP343high8.4CVSS 3.1
AVLACLPRLUINSCCHIHAN
EPSS
0.09%
0.6th percentile
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.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| ibm | sterling_connect_direct_for_unix | 6.3.0.0 – 6.3.0.7 | — |
| ibm | sterling_connect_direct_for_unix | 6.4.0.0 – 6.4.0.6 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
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.
ghsa_unreviewed·2026-10-20
CVE-2026-105453 [HIGH] CWE-269 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.
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.
VulDB
IBM Sterling Connect Direct for Unix up to 6.3.0.7/6.4.0.6 privileges management
vuldb·2026-10-20·CVSS 8.4
CVE-2026-105453 [HIGH] IBM Sterling Connect Direct for Unix up to 6.3.0.7/6.4.0.6 privileges management
A vulnerability has been found in IBM Sterling Connect Direct for Unix up to 6.3.0.7/6.4.0.6 and classified as problematic. This vulnerability affects unknown code. The manipulation leads to improper privilege management.
This vulnerability is traded as CVE-2026-105453. An attack has to be approached locally. There is no exploit available.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-10-20
Published