Sensitive information in log files in IBM API Connect
Priority MEDIUM 46CWE-532Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-532.
Summary
API Connect V2018.1 through 2018.4.1.1 is impacted by access token leak. Authorization tokens in some URLs can result in the tokens being written to log files. IBM X-Force ID: 155626.
Why it matters now
EPSS 0.02272 83rd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2019-4008
- 2026-10-03 Alias added: GHSA-hg9m-423c-v2w6
References
More IBM Api Connect vulnerabilities
- TI-2025-12717 Authentication bypass in IBM API Connect CVSS 3.1CRITICAL 9.8
- TI-2019-03132 OS command injection in IBM API Connect CVSS 3.1CRITICAL 10.0
- TI-2026-07972 IBM API Connect SQL Injection CVSS 3.1CRITICAL 9.8
- TI-2019-03106 IBM API Connect's Developer Portal 2018.1 and 2018.4.1.3 is impacted by a privilege… CVSS 3.0CRITICAL 9.8
- TI-2018-01353 IBM API Connect Developer Portal 5.0.0.0 through 5.0.8.2 could allow an unauthenticated… CVSS 3.0CRITICAL 9.8
- TI-2019-03133 Server-side request forgery in IBM API Connect CVSS 3.1CRITICAL 9.8
Sources
- CVE-2019-4008 · CVE Program
- CVE-2019-4008 · NVD
- FIRST EPSS
- GHSA-hg9m-423c-v2w6 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences