dbcve.org
Db2Application · Ibm

CVE-2025-36425

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-17
Fix available
A fix is available. Upgrade to after 12.1.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 for Linux, UNIX and Windows (includes Db2 Connect Server) 11.5.0 through 11.5.9 and 12.1.0 through 12.1.3 could allow an authenticated user to obtain sensitive information under specific HADR configuration.

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.3 contain an information disclosure vulnerability specific to HADR (High Availability Disaster Recovery) configurations. An authenticated database user can potentially obtain sensitive information through certain HADR setup scenarios.

MitigationRestrict HADR configuration access to essential administrative personnel only. Monitor for unauthorized access attempts to HADR metadata. Apply vendor patches when available and review HADR configuration settings for exposure of sensitive data.

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.3

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. Check installed Db2 version
    Run `db2level` or query `SYSIBMADM.DBMCFG` for the `service_level` parameter to obtain the exact version number
    Affected if Version is 11.5.0 through 11.5.9 OR 12.1.0 through 12.1.3
  2. Verify if HADR is configured
    Query the HADR status using `db2pd -db <databasename> -hadr` or check the database configuration for HADR-related parameters such as `HADR_LOCAL_HOST`, `HADR_REMOTE_HOST`, and `HADR_ROLE`
    Affected if HADR is configured and active on the database instance
  3. Identify HADR primary and standby setup
    Check the HADR role configuration by inspecting `HADR_ROLE` database configuration parameter - values include PRIMARY, STANDBY, or both if peer catchup mode is in use
    Affected if HADR is set up with PRIMARY and STANDBY roles, as the vulnerability affects certain HADR setup scenarios
  4. Inspect HADR connection metadata
    Review output from `db2pd -db <dbname> -hadr -conn` to examine active HADR connections and metadata exchanges between primary and standby systems
    Affected if Active HADR connections exist where sensitive configuration or authentication metadata may be exposed during certain setup scenarios

User is affected if Db2 version falls within 11.5.0-11.5.9 or 12.1.0-12.1.3 AND HADR is configured, as the information disclosure vulnerability is specific to HADR setup scenarios.

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 a release after 12.1.3
Interim mitigation

Restrict HADR configuration access to essential administrative personnel only. Monitor for unauthorized access attempts to HADR metadata. Apply vendor patches when available and review HADR configuration settings for exposure of sensitive data.

Recommended fix Moderate confidence

Db2 11.5.10+ or 12.1.4+ (or latest available release)

  1. 1. Identify your current Db2 version by running 'db2level' command
  2. 2. For Db2 11.5.x: Upgrade to Db2 11.5.10 or later (or migrate to 12.1.0+)
  3. 3. For Db2 12.1.x: Upgrade to Db2 12.1.4 or later (or migrate to 12.2.0+)
  4. 4. Download the appropriate fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  5. 5. Apply the fix pack following IBM's standard Db2 upgrade procedure
  6. 6. Verify the upgrade was successful by running 'db2level'
  7. 7. Test HADR functionality to ensure the fix addresses the sensitivity issue
Caveat Review IBM Db2 upgrade documentation for compatibility considerations between versions; test applications against new version before production deployment

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

Fix this in Db2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36425 — 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-36425 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