# CVE-2025-14115: Hardcoded credentials in Sterling Connect:Direct for UNIX Container

> IBM Sterling Connect:Direct for UNIX Container contains hard-coded credentials, allowing attackers to bypass authentication or access internal data.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-vwv8-6f5h-57m5

## What is CVE-2025-14115?

CVE-2025-14115 is a high-severity vulnerability in IBM Sterling Connect:Direct for UNIX Container, published on 20 Jan 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 Container 6.3.0.0 through 6.3.0.6 Interim Fix 016, and 6.4.0.0 through 6.4.0.3 Interim Fix 019 IBM® Sterling Connect:Direct for UNIX contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2025-14115?


## How do I fix CVE-2025-14115?

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

## Is CVE-2025-14115 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14115 and fix it if it is affected.

What it is: CVE-2025-14115 is a high-severity vulnerability in IBM Sterling Connect:Direct for UNIX Container, published on 20 Jan 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-2025-14115 in the wild and no public exploit code.

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

## Sources

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

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