Skip to main content

IBM Db2 EUVDEUVD-2026-57619

| CVE-2026-18097 MEDIUM
Insertion of Sensitive Information into Log File (CWE-532)
2026-08-12 ibm GHSA-q83p-h7pj-3m3p
5.5
CVSS 3.1 · Vendor: ibm
Share

Severity by source

Vendor (ibm) PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI
5.5 MEDIUM

Local low-privilege OS access suffices to read trace files; only confidentiality is impacted as passwords are exposed with no write or availability consequence.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Analysis Generated
Aug 12, 2026 - 21:41 vuln.today
CVE Published
Aug 12, 2026 - 20:48 nvd
MEDIUM 5.5

DescriptionCVE.org

IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 for Linux, UNIX and Windows (includes DB2 Connect Server) could allow a local attacker to obtain sensitive information due to the logging of plain text passwords in trace files.

AnalysisAI

IBM Db2 on Linux, UNIX, and Windows exposes cleartext database passwords by writing them into diagnostic trace files, affecting versions 11.5.0-11.5.9 and 12.1.0-12.1.5, including DB2 Connect Server. Any low-privilege local OS user with read access to the Db2 trace directory can harvest plaintext credentials without requiring database-level authentication or elevated system rights. IBM has released a patch; no active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis.

Technical ContextAI

IBM Db2 is a widely deployed enterprise relational database management system for Linux, UNIX, and Windows, identified by CPE cpe:2.3:a:ibm:db2:*:*:*:*:*:*:*:*. The vulnerability is rooted in CWE-532 - Insertion of Sensitive Information into Log File - where the Db2 tracing subsystem records diagnostic output that includes authentication credentials in plain, unredacted text. Trace files are written to host filesystem paths typically under the Db2 instance directory. DB2 Connect Server, included in the affected scope, acts as a gateway for mainframe and midrange database connectivity, making it a particularly sensitive target as it may broker credentials for multiple upstream systems. The core failure is the absence of sanitization or masking of password material prior to writing to persistent trace output.

RemediationAI

Apply the IBM-released patch per the vendor advisory at https://www.ibm.com/support/pages/node/7282952; the exact patched version should be confirmed directly in that advisory, as it was not specified in available intelligence data. While patching, restrict filesystem permissions on Db2 trace file directories to the db2 instance owner and dedicated DBA accounts only, preventing low-privilege OS users from reading trace output - note this may complicate future diagnostic work by non-DBA support personnel. Disable tracing when not actively performing diagnostics, treating trace collection as a privileged operational action requiring explicit authorization. Audit existing trace files for captured credential strings and rotate all potentially exposed database passwords immediately. On DB2 Connect Server deployments, prioritize remediation given that compromised credentials may grant access to multiple connected backend systems.

More in Db2

View all
CVE-2012-4826 HIGH
8.5 Oct 20

Stack-based buffer overflow in the SQL/PSM (aka SQL Persistent Stored Module) Stored Procedure (SP) infrastructure in IB

CVE-2017-1297 HIGH POC
7.3 Jun 27

IBM DB2 for Linux, UNIX and Windows 9.2, 10.1, 10.5, and 11.1 (includes DB2 Connect Server) is vulnerable to a stack-bas

CVE-2014-3094 HIGH
8.5 Sep 04

Stack-based buffer overflow in IBM DB2 9.7 through FP9a, 9.8 through FP5, 10.1 through FP4, and 10.5 before FP4 on Linux

CVE-2012-1797 CRITICAL
10.0 Mar 20

IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors. Rated critic

CVE-2026-10109 CRITICAL
9.8 Jun 30

Remote code execution in IBM Db2 11.5.0-11.5.9 and 12.1.0-12.1.4 lets unauthenticated network attackers run arbitrary co

CVE-2026-10543 CRITICAL
9.8 Aug 12

Privilege escalation in IBM Db2 (data server versions 11.5.0-11.5.9 and 12.1.0-12.1.5) allows an attacker to submit a sp

CVE-2026-10534 CRITICAL
9.8 Aug 12

Memory-corruption in IBM Db2's IXF file IMPORT parser lets an attacker supply a crafted IXF data file that overflows a s

CVE-2012-2197 HIGH
7.1 Jul 25

Stack-based buffer overflow in the Java Stored Procedure infrastructure in IBM DB2 9.1 before FP12, 9.5 through FP9, 9.7

CVE-2012-3324 CRITICAL
9.0 Sep 25

Directory traversal vulnerability in the UTL_FILE module in IBM DB2 and DB2 Connect 10.1 before FP1 on Windows allows re

CVE-2018-1426 CRITICAL
9.1 Mar 22

IBM GSKit (IBM DB2 for Linux, UNIX and Windows 9.7, 10.1, 10.5, and 11.1) duplicates the PRNG state across fork() system

CVE-2012-0711 HIGH
7.5 Mar 20

Integer signedness error in the db2dasrrm process in the DB2 Administration Server (DAS) in IBM DB2 9.1 through FP11, 9.

CVE-2013-6744 HIGH
8.5 May 30

The Stored Procedure infrastructure in IBM DB2 9.5, 9.7 before FP9a, 10.1 before FP3a, and 10.5 before FP3a on Windows a

Share

EUVD-2026-57619 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy