dbcve.org
Db2Application · Ibm

CVE-2026-1577

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-30
Fix available
A fix is available. Upgrade to after 12.1.4 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 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 allow an authenticated user to cause a denial of service due to improper neutralization of special elements in data query logic.

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 (including Db2 Connect Server) contain a denial of service vulnerability. An authenticated user can send specially crafted queries containing special elements that are not properly neutralized in the data query logic, causing the database service to become unavailable.

MitigationApply IBM's patched Db2 version (beyond 11.5.9 and 12.1.4) or install the available interim fix. As a compensating control, restrict database access to trusted authenticated users and monitor for abnormal query patterns.

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
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. Identify installed Db2 version
    Run 'db2level' command from a Db2 instance owner or query 'SELECT GETVARIABLE('SYSINSTALLOBJECTS.VERSION')' from a connected session
    Affected if The version number falls within 11.5.0-11.5.9 or 12.1.0-12.1.4
  2. Confirm Db2 edition and platform
    Run 'db2pd -db <dbname>' or check installation details via 'db2licm -l' to confirm edition and platform type (Linux, UNIX, or Windows)
    Affected if The installation is Db2 on Linux, UNIX, or Windows (including Db2 Connect Server) within the affected version range
  3. Verify authenticated user access is enabled
    Check database configuration parameter 'AUTHENTICATION' via 'get dbm cfg' or 'SELECT * FROM SYSIBMADM.DBCFG' to confirm client authentication mode
    Affected if Authentication is set to a mode that permits client-side authentication (CLIENT, KERBEROS, or similar) rather than SERVER_ENCRYPT, meaning authenticated users can connect
  4. Confirm query execution is available to standard users
    Review database privileges: run 'SELECT GRANTOR, GRANTEE, DBADMAUTH FROM SYSCAT.DBAUTH' and check if regular users have CONNECT or DATAACCESS privileges
    Affected if Non-admin authenticated users have CONNECT or DATAACCESS privileges and can execute queries against user tables
  5. Check for recent service disruptions or query failures
    Review db2diag.log files in <db2home>/sqllib/db2dump/ for patterns of abends, crashes, or SQL error codes related to query processing
    Affected if There are recent entries showing service unavailability or query processing failures correlating with the timeline of this vulnerability

The environment is affected if Db2 version is 11.5.0 through 11.5.9 or 12.1.0 through 12.1.4 on Linux/UNIX/Windows, and authenticated users can execute arbitrary queries against the database.

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.4
Interim mitigation

Apply IBM's patched Db2 version (beyond 11.5.9 and 12.1.4) or install the available interim fix. As a compensating control, restrict database access to trusted authenticated users and monitor for abnormal query patterns.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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