API Connect: Use of Default Credentials
CVE-2026-3144 is a critical-severity use of default credentials vulnerability in API Connect from IBM, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 12.1.0.3 as the first without the flaw, so updating API Connect to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.41% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update API Connect to 12.1.0.3 or a later version.
- Read the advisory on ibm.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| IBM | API Connect | 12.1.0.0 up to, but not including, 12.1.0.3 | 12.1.0.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.1 | High | CNA (us.ibm.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
IBM API Connect 12.1.0.0 through 12.1.0.3 uses default credentials which could allow an attacker to gain unauthorized access to the application before the system enforces a credential update.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use of Default Credentials
The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
How developers prevent this class of flaw
- Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.
- Force the administrator to change the credential upon installation.
- The product administrator could change the defaults upon installation or during operation.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in API Connect
- 7.2 High severity
- 7.5 High severity
- 8.3 High severity
- 9.4 Critical severity
- 9.3 Critical severity
- 9.6 Critical severity
Recent Use of Default Credentials vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 7.5 High severity
Spotted an error? Tell us.