dbcve.org
Db2Application · Ibm

CVE-2026-1352

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-23
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 for Linux, UNIX, and Windows contain a vulnerability where authenticated users can trigger a denial of service via improper neutralization of special elements in data query logic, likely allowing maliciously crafted SQL to cause service disruption.

MitigationUpgrade IBM Db2 to a version beyond 11.5.9 and 12.1.4, or apply the appropriate interim fix/FP from IBM. Implement least-privilege database user accounts and restrict query execution permissions until patching is complete.

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 if IBM Db2 is installed
    Run 'db2start' or check for Db2 processes with 'ps -ef | grep db2sysc' on Linux/UNIX, or check Services on Windows. Also look for Db2 installation directories like /opt/ibm/db2 or C:\Program Files\IBM\DB2'.
    Affected if IBM Db2 database server is present on the system
  2. Determine the installed Db2 version
    Run 'db2level' command as the Db2 instance user, or query with 'db2 select * from sysibmadm.env_cfg_info'
    Affected if The version output shows 11.5.x where x is 0-9, or 12.1.x where x is 0-4
  3. Confirm version is within affected ranges
    Compare the version from step 2 against: 11.5.0 through 11.5.9 inclusive, or 12.1.0 through 12.1.4 inclusive
    Affected if Installed version falls within 11.5.0-11.5.9 or 12.1.0-12.1.4
  4. Check database authentication is enabled
    Verify that Db2 authentication is configured by running 'db2 get dbm cfg | grep AUTHENTICATION'
    Affected if Authentication is set to anything other than NONE, meaning users require credentials to connect
  5. Assess network exposure
    Check if the Db2 port (typically 50000 or 50001) is exposed externally via 'netstat -an | grep 5000' or review firewall rules
    Affected if Db2 listener is bound to external interfaces and reachable from untrusted networks

You are affected if IBM Db2 is installed and the version falls within 11.5.0-11.5.9 or 12.1.0-12.1.4, regardless of authentication configuration, since the flaw is exploitable by any authenticated user.

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

Upgrade IBM Db2 to a version beyond 11.5.9 and 12.1.4, or apply the appropriate interim fix/FP from IBM. Implement least-privilege database user accounts and restrict query execution permissions until patching is complete.

Recommended fix Moderate confidence

Db2 11.5.10+ or 12.1.5+ (any version beyond the affected range)

  1. Review IBM Db2 fix packs and security bulletins at www.ibm.com for CVE-2026-1352
  2. Download and install the appropriate Db2 fix pack that addresses this vulnerability
  3. For Db2 11.5.x, install version 11.5.10 or later
  4. For Db2 12.1.x, install version 12.1.5 or later
  5. Test the upgrade in a non-production environment before applying to production
  6. Apply the fix pack following IBM's standard Db2 update procedures
  7. Verify the fix by checking that the vulnerability is resolved
Caveat Review IBM Db2 release notes for potential compatibility changes between versions; test applications thoroughly after upgrade

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

Fix this in Db2 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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