Skip to content
major vulnerability· requires attention

Widely-used enterprise file transfer product; hard-coded credentials enable persistent access and data exposure.

Applications

CVE-2025-14115

8.4
High
EPSS 0.10%Patch availableJan 21, 2026

Hard-coded credentials enable auth bypass in IBM Sterling Connect:Direct UNIX

common questions

Is CVE-2025-14115 being exploited?

Not confirmed. CVE-2025-14115 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.10% probability of exploitation in the next 30 days.

How severe is CVE-2025-14115?

CVE-2025-14115 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-14115?

Yes. A fix has been recorded for CVE-2025-14115. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-14115 affect?

CVE-2025-14115 affects IBM Sterling Connect:Direct for UNIX Container (6.3.x IF016, 6.4.x IF019). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-14115?

Patch to fixed IF 016/019 and rotate credentials

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
IBM Sterling Connect:Direct for UNIX Container (6.3.x IF016, 6.4.x IF019)
impact

Authentication bypass via fixed credentials, enabling access to inbound/outbound channels and internal data.

action required

Immediate action required

affected versions
IBM Sterling Connect:Direct for UNIX Container
  • affected>= 6.3.0.0 and <= 6.3.0.6 Interim Fix 016
  • affected>= 6.4.0.0 and <= 6.4.0.3 Interim Fix 019

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free