CVE-2026-1718
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 · uneditedIBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.4 is vulnerable to a denial of service with a specially crafted query when autonomous transactions are enabled.
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 confidenceIBM Db2 versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.4 contain a denial of service vulnerability exploitable via specially crafted SQL queries when the autonomous transactions feature is enabled. The malformed query triggers a condition that causes the database service to become unavailable.
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>= 11.5.0, <= 11.5.9>= 12.1.0, <= 12.1.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Db2 versionUse Db2 version retrieval commands (such as db2level, db2pd, or SELECT statements against system catalog) to determine the exact installed version and build levelAffected if version is 11.5.0 through 11.5.9 OR 12.1.0 through 12.1.4
-
Confirm autonomous transactions feature statusQuery Db2 configuration settings, registry variables, or database manager parameters to determine whether autonomous transactions are enabled. This may involve checking DB2 configuration files, db2set commands, or querying system views related to transaction managementAffected if autonomous transactions are currently enabled in the Db2 configuration
Environment is affected only if both the installed Db2 version falls within the vulnerable ranges AND autonomous transactions feature is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply IBM Db2 patches for this vulnerability; if patches are unavailable, evaluate disabling autonomous transactions if business requirements permit, or upgrade to a fixed version.
Db2 11.5.10 or later; Db2 12.1.5 or later (upgrade to the next fix pack beyond the affected ranges)
- 1. Verify current Db2 version by running: db2pd -version or SELECT * FROM SYSIBMADM.SYSDBENV
- 2. Confirm autonomous transactions are enabled by checking the database configuration: db2 get db cfg for <database_name> | grep -i autonom
- 3. Schedule a maintenance window for the upgrade process
- 4. Backup all databases before proceeding with the upgrade
- 5. Download and install the latest Db2 fix pack for your version line (11.5.10+ or 12.1.5+) from IBM Fix Central: https://www.ibm.com/support/fixcentral/
- 6. Apply the fix pack using IBM's installation instructions for your operating system
- 7. After upgrade, verify the vulnerability is resolved by confirming the version: db2pd -version
- 8. Test that autonomous transaction functionality works correctly with your applications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1718 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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