CVE-2026-18668
Protection Mechanism Failure vulnerability affects IBM Sterling File Gateway
IBM Sterling File Gateway 6.2.1.0 through 6.2.1.2_1 and 6.2.2.0 - 6.2.2.1_1 could allow a remote attacker to perform protocol downgrade attacks due to a security misconfiguration.
Fixes and workarounds
Fix
ProductVersionAPARRemediation & Fix IBM Sterling File Gateway 6.2.1.0 - 6.2.1.2_1IT49752 Apply 6.2.1.3 IBM Sterling File Gateway 6.2.2.0 - 6.2.2.1_1IT49752 Apply 6.2.2.2 The IIM versions of 6.2.1.3 and 6.2.2.2 are available on Fix Central http://www-933.ibm.com/support/fixcentral/swg/selectFixes . The container versions of 6.2.1.3 and 6.2.2.2 are available in IBM Entitled Registry * cp.icr.io/cp/ibm-b2bi for IBM Sterling File Gateway
Source: CNA: ibmFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: ibmAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Sterling File Gateway IBM |
≥ 6.2.1.0; ≤ 6.2.1.2_1, 6.2.2.0 - 6.2.2.1_1 (affected, semver) | CNA: ibm |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 6.5 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | CNA: ibm |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.ibm.com/support/pages/node/7294084CNA: ibm · vendor-advisory, patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.