Security Resilience

CVE-2026-1248

Info Disclosure in Ibm Business Automation Workflow 24.0.0 … 25.0.1

Published
27 May 2026
Modified
14 October 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0022 13th percentile
Risk Priority 35 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-1248 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Ibm Business Automation Workflow. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Domain Accounts (T1078.002); ranked at the 13th 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 SI-11 (Error Handling) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Business Automation Workflow containers and traditional may leak information about its database structure in error messages.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1078.002 Domain Accounts Stealth
Adversaries may obtain and abuse credentials of a domain account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
T1589.001 Credentials Reconnaissance
Adversaries may gather credentials that can be used during targeting.
T1589.003 Employee Names Reconnaissance
Adversaries may gather employee names that can be used during targeting.
T1592 Gather Victim Host Information Reconnaissance
Adversaries may gather information about the victim's hosts 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-2025-1495Same product: Ibm Business Automation Workflow
CVE-2025-36058Same product: Ibm Business Automation Workflow
CVE-2025-13096Same product: Ibm Business Automation Workflow
CVE-2024-38321Same product: Ibm Business Automation Workflow
CVE-2023-24957Same product: Ibm Business Automation Workflow
CVE-2024-54179Same product: Ibm Business Automation Workflow
CVE-2023-50953Same vendor: Ibm
CVE-2024-51460Same vendor: Ibm
CVE-2024-45658Same vendor: Ibm
CVE-2024-52893Same vendor: Ibm

Affected Assets

ibm
business automation workflow
24.0.0, 24.0.1, 25.0.0, 25.0.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V16.5.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

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 require sanitized error handling to prevent sensitive data disclosure.

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

Security testing can detect error messages that leak sensitive information.

prevents

Secure coding standards explicitly forbid exposing sensitive data in errors.

removes

A.8.9's templates and configuration enforcement can remove configuration-level instances of CWE-209 (e.g., disabling verbose error pages, suppressing debug output, setting generic error responses), but cannot reach the majority of instances where application code explicitly constructs error messages containing sensitive data — those require code changes the clause does not perform.

References