Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2026-5515 is a medium-severity Insecure Storage of Sensitive Information (CWE-922) vulnerability in Ibm App Connect Enterprise. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Credentials In Files (T1552.001); ranked at the 1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-6 (Least Privilege) and AU-9 (Protection of Audit Information) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-32461
Vulnerability Data
IBM App Connect Enterprise 13.0.1.0 through 13.0.7.0 stores potentially sensitive information in log files that could be read by a local user.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Log file exposure of sensitive data directly enables reading unsecured credentials from local files.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires protection of log/audit files against unauthorized local read access, addressing the core exposure of sensitive data in logs.
Enforces least-privilege file permissions so that only authorized accounts can read the application log files containing sensitive information.
Requires cryptographic or access protections for sensitive data at rest, which can be applied to log files to prevent local disclosure.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforces least-privilege permissions and authorization reviews that limit read/write access to stored sensitive data.
Directly protects data-at-rest confidentiality via encryption or access controls that prevent unauthorized reads.
Secure SDLC practices directly prohibit writing sensitive data to logs; eliminating the weakness satisfies only one narrow slice of the control.
Log generation configuration can and should exclude sensitive data, but the control statement focuses on availability rather than content filtering.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Requiring de-identification and privacy controls before logs leave the organization reduces the chance that sensitive data inadvertently captured in logs becomes exposed to external parties.
By defining what records must be kept, where, and for how long, the control discourages the inadvertent inclusion of sensitive information in logs or other externally accessible files that fall outside the formal record system.
Mandating deletion of temporary files and logs that may contain sensitive information prevents those artifacts from remaining accessible after the data is no longer needed.
When log entries are produced from masked data sets, the control prevents the inadvertent insertion of sensitive values into externally accessible log files.
DLP inspection of logs and file transfers can detect and block the inadvertent placement of sensitive tokens or credentials into externally accessible log files before they are written or transmitted.
Requiring restrictions on free-text fields and proper error-message handling stops developers from embedding or leaking sensitive data into logs or diagnostic output.