Account compromise via missing CLIENT lockout
Published Sep 22, 2025 · Updated Mar 13, 2026
Improper account lockout in IBM Sterling Connect:Express for Microsoft Windows 3.1.0.0 through 3.1.0.22 allows remote attackers to guess credentials. The CLIENT authentication path accepts repeated bad credentials without locking the targeted account, allowing unrestricted password attempts. A network-reachable CLIENT login is sufficient; success requires guessing valid credentials and exposes data available to the compromised account.
Summary
What happened
Improper account lockout in IBM Sterling Connect:Express for Microsoft Windows 3.1.0.0 through 3.1.0.22 allows remote attackers to guess credentials. The CLIENT authentication path accepts repeated bad credentials without locking the targeted account, allowing unrestricted password attempts. A network-reachable CLIENT login is sufficient; success requires guessing valid credentials and exposes data available to the compromised account.
The record
- CVE
- CVE-2025-36064
- Published
- Sep 22, 2025
- Updated
- Mar 13, 2026
- Vendor
- IBM
- Product
- IBM Sterling Connect:Express for Microsoft Windows
- Classifications
- CWE-307, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 22, 2025CVE publishedPublication date reported by the CVE source.
- Mar 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.1.0.0 <=3.1.0.22
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo