dbcve.org
Db2Application · Ibm

CVE-2025-3050

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-29
Fix available
A fix is available. Upgrade to after 12.1.1 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.1 could allow an authenticated user to cause a denial of service when using Q replication due to the improper allocation of CPU resources.

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 · high confidence

IBM Db2 versions 11.5.0-11.5.9 and 12.1.0-12.1.1 contain a denial of service vulnerability in the Q replication feature where authenticated users can trigger improper CPU resource allocation, potentially causing the database or replication services to become unresponsive.

MitigationApply the appropriate IBM Db2 patch or upgrade to a fixed version beyond 11.5.9 or 12.1.1. Review Q replication configurations and monitor resource utilization during remediation.

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, <= 11.5.9>= 12.1.0, <= 12.1.1

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
None
Integrity
None
Availability
High

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

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 the 'db2level' command from a Db2 command prompt or query SYSCAT.ENVIRONMENT_INFO to obtain the exact version and fix pack level
    Affected if The installed version is 11.5.0 through 11.5.9, or 12.1.0 through 12.1.1
  2. Verify Q replication is configured
    Query the Q replication catalog tables (such as ASNCDC.REGISTERED_TABLES or ASN.IBMQREP_SUBS) or use 'asnqqcap' command to list Q replication subscriptions
    Affected if Q replication subscriptions or paths are actively configured in the database
  3. Confirm Q replication processes are running
    Check for active Q capture (asnqcap) and Q apply (asnqapp) processes on the system using process listing or Db2 monitoring commands
    Affected if Q replication capture or apply processes are currently running

Environment is affected if running a vulnerable Db2 version (11.5.0-11.5.9 or 12.1.0-12.1.1) with Q replication feature actively configured or running

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.

From vendor data
Upgrade available Upgrade to a release after 12.1.1
Interim mitigation

Apply the appropriate IBM Db2 patch or upgrade to a fixed version beyond 11.5.9 or 12.1.1. Review Q replication configurations and monitor resource utilization during remediation.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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