Security Resilience

CVE-2026-5515

Info Disclosure in Ibm App Connect Enterprise 13.0.1.0 – 13.0.7.1

Published
27 May 2026
Modified
14 October 2026
Patch / advisory
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0010 0.9th percentile
Risk Priority 41 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

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 Local Accounts (T1078.003); ranked at the 0.9th 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-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

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 Techniques

MITRE ATT&CK v20.0

T1078.003 Local Accounts Stealth
Adversaries may obtain and abuse credentials of a local account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1552.003 Shell History Credential Access
Adversaries may search the command history on compromised systems for insecurely stored credentials.
T1552.007 Container API Credential Access
Adversaries may gather credentials via APIs within a containers environment.
T1589.001 Credentials Reconnaissance
Adversaries may gather credentials that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-12947Same product: Ibm App Connect Enterprise
CVE-2023-40682Same product: Ibm App Connect Enterprise
CVE-2026-14522Same product: Ibm App Connect Enterprise
CVE-2026-15435Same product: Ibm App Connect Enterprise
CVE-2024-31904Same product: Ibm App Connect Enterprise
CVE-2024-22317Same product: Ibm App Connect Enterprise
CVE-2026-14519Same product: Ibm App Connect Enterprise
CVE-2024-28760Same product: Ibm App Connect Enterprise
CVE-2025-0799Same product: Ibm App Connect Enterprise
CVE-2024-31895Same product: Ibm App Connect Enterprise

Affected Assets

ibm
app connect enterprise
13.0.1.0 — 13.0.7.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Enforces approved authorizations for logical access to stored information, directly stopping unauthorized read/write.

Requires protection of confidentiality/integrity for information at rest, directly addressing insecure storage.

Limits privileges so only authorized accesses to sensitive stored data are permitted.

Associates security attributes with information to support proper access decisions on storage.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prohibit writing sensitive data to logs; eliminating the weakness satisfies only one narrow slice of the control.

PR.PS-04 partial match
blocks

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)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's SOURCE reach (SAST, code review) catches the bulk of CWE-532 instances where sensitive data is passed directly to logging calls, and RUNTIME reach (penetration testing) can surface sensitive data in accessible logs; the remainder is bounded and nameable — cases where sensitivity is context-dependent and not flagged by configured rules, and indirect logging patterns (e.g., logging entire objects whose toString() exposes sensitive fields) that SAST rules miss.

prevents

A.8.28 mandates secure coding practices that include guidance on what not to log (sensitive data is exactly the kind of 'common and historical coding practice' the clause names), but the mechanism is human practice — developers must know what counts as sensitive, redact it, and apply that consistently across error paths and third-party libraries. This is the same practice-not-mechanism reading that graded A.8.28 -> CWE-79 and A.8.28 -> CWE-502 at `partial`, and the clause carries a declared ceiling of `partial` on this verb for code-level defects.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-922, a class-level weakness. Rules are authored against its narrower children: CWE-312.

References