dbcve.org
Db2Application · Ibm

CVE-2025-33092

HIGH · 7.8 CVSS v3.1 Published 2025-07-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 12.1.0, 12.1.1, and 12.1.2 is vulnerable to a stack-based buffer overflow in db2fm, caused by improper bounds checking. A local user could overflow the buffer and execute arbitrary code on the system.

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 for Linux versions 12.1.0, 12.1.1, and 12.1.2 contain a stack-based buffer overflow vulnerability in the db2fm (Db2 Fault Monitor) component due to improper bounds checking. A local authenticated user can exploit this to overflow the stack buffer and execute arbitrary code with elevated privileges.

MitigationApply IBM's security patch for this vulnerability. Refer to IBM's official security bulletin for the corrected Db2 version and follow the standard Db2 maintenance update procedure.

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:= 12.1.0= 12.1.1= 12.1.2

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 IBM Db2 version
    Run 'db2pd -version' or 'db2level' command as the Db2 instance owner to retrieve the installed Db2 version number
    Affected if The version displayed is 12.1.0, 12.1.1, or 12.1.2 specifically
  2. Verify db2fm component presence
    Check if the db2fm (Db2 Fault Monitor) binary exists on the system, typically in the Db2 installation bin directory (for example, ls -la /opt/ibm/db2/V12.1/bin/db2fm or similar path under your Db2 installation)
    Affected if The db2fm binary is present and executable on the system
  3. Check db2fm service status
    Run 'db2fm -s' or 'db2fm -L' as the Db2 instance owner to check if the Fault Monitor service is running or configured
    Affected if The db2fm service is active, running, or enabled on the host
  4. Confirm Db2 installation on Linux
    Query the system package manager (rpm -qa | grep -i db2 or dpkg --list | grep -i db2) or check for Db2 installation directories under /opt/ibm/
    Affected if IBM Db2 version 12.1.0, 12.1.1, or 12.1.2 is installed on a Linux system

You are affected if IBM Db2 version 12.1.0, 12.1.1, or 12.1.2 is installed on Linux and the db2fm (Db2 Fault Monitor) component is present and accessible on the system.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's security patch for this vulnerability. Refer to IBM's official security bulletin for the corrected Db2 version and follow the standard Db2 maintenance update procedure.

Fix this in Db2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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