Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
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 Databases (T1213.006); 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) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-32521
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 TechniquesAI
Why these techniques?
CWE-209 error message leak directly exposes database schema details, enabling T1213.006 data collection from databases.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires error messages to be constructed so they do not reveal sensitive information such as database structure details.
Filters outbound information to suppress sensitive data that would otherwise appear in error responses.
Mandates timely remediation of the software flaw that causes generation of overly verbose error messages.
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.
Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.
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.
Secure coding standards explicitly forbid exposing sensitive data in errors.
Security testing can detect error messages that leak sensitive information.
Logging policy can require suppression of sensitive data in error messages.
Secure SDLC mandates error-handling rules that avoid leaking sensitive information.
Application security requirements can specify safe error messaging.
Secure architecture principles include proper exception handling.