dbcve.org
Db2Application · Ibm

CVE-2025-36372

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 11.5.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 for Linux, UNIX and Windows (includes Db2 Connect Server) could disclose sensitive information to an authenticated user from the monitoring and event tables.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IBM Db2 versions 11.5.0-11.5.9 and 12.1.0-12.1.4 on Linux, UNIX, and Windows contain a vulnerability in monitoring and event tables that allows authenticated users to access sensitive information they should not have permission to view.

MitigationApply IBM's security patches for this vulnerability or upgrade to a fixed version of Db2 (11.5.10+ or 12.1.5+). Review and restrict access to monitoring and event tables as an interim control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Db2Application
Affected:>= 11.5.0, < 11.5.9>= 12.1.0, <= 12.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Db2 version
    Run 'db2level' from a Db2 command prompt or check the installation directory for version information. On Linux/UNIX, also check '/opt/ibm/db2/version' or use 'db2pd -version'. On Windows, check the Db2 installation via Control Panel or 'db2register' output.
    Affected if The installed version is 11.5.0 through 11.5.9, or 12.1.0 through 12.1.4.
  2. Verify monitoring and event tables are present
    Connect to the database as an authenticated user and query the system catalog for monitoring tables. Run: SELECT TABNAME FROM SYSCAT.TABLES WHERE TABSCHEMA = 'SYSTOOLS' AND TABNAME LIKE '%MON%' OR TABSCHEMA = 'SYSCAT' AND TABNAME LIKE '%EVENT%';
    Affected if The database contains SYSTOOLS monitoring tables or SYSCAT event tables accessible to standard database users.
  3. Check user permissions on monitoring tables
    Run: SELECT GRANTOR, GRANTEE, TABNAME, PRIVILEGE FROM SYSCAT.TABPRIV WHERE TABSCHEMA IN ('SYSTOOLS', 'SYSCAT') AND TABNAME LIKE '%MON%' OR TABSCHEMA = 'SYSCAT' AND TABNAME LIKE '%EVENT%'; to see which users have access to sensitive monitoring and event tables.
    Affected if Non-admin users or users outside the DBADM group have SELECT or other privileges on monitoring/event tables they should not access.
  4. Audit access to sensitive monitoring views
    Query for users with access to SYSCAT.MON_GET_* tables or equivalent monitoring views: SELECT GRANTEE, TABNAME FROM SYSCAT.TABPRIV WHERE TABNAME LIKE 'MON_GET%' OR TABNAME LIKE 'MON$%';
    Affected if Regular authenticated users have been granted access to MON_GET or MON$ prefixed tables/views.

A user is affected if their Db2 version falls within 11.5.0-11.5.9 or 12.1.0-12.1.4 AND authenticated non-privileged users have access to monitoring or event tables containing sensitive data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.5.9 or later
Fixed in 11.5.9
Interim mitigation

Apply IBM's security patches for this vulnerability or upgrade to a fixed version of Db2 (11.5.10+ or 12.1.5+). Review and restrict access to monitoring and event tables as an interim control.

Recommended fix Moderate confidence

Db2 11.5.9+ or 12.1.5+ (depending on your current major version)

  1. 1. Identify the current IBM Db2 version installed using: db2pd -version or db2look -d <database> -version
  2. 2. For Db2 11.5.x: Plan upgrade to Db2 11.5.9 or later (minimum fixed release)
  3. 3. For Db2 12.1.x: Plan upgrade to Db2 12.1.5 or later (minimum fixed release)
  4. 4. Review IBM Db2 upgrade documentation for your specific platform (Linux, UNIX, or Windows)
  5. 5. Schedule maintenance window for the upgrade process
  6. 6. Perform full backup of all databases before upgrade
  7. 7. Execute upgrade following IBM's standard upgrade procedures
  8. 8. Verify successful upgrade by running: db2pd -version and connecting to databases
Caveat Standard Db2 upgrade considerations apply - review IBM's upgrade guide for migration requirements, deprecated features, and compatibility settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Db2 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36372 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data