Skip to main content
CVE-2025-2533VulnerabilityPublished

CVE-2025-2533: IBM Db2 · Uncontrolled Memory Allocation

Affects IBM Db2Source CVE Database V5

0

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Ibmibm/db2pkg:deb/ibm/db2Other threatsAffected
  • =12.1.0
  • =12.1.1
  • =12.1.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should prioritize the following actions: 1) Monitor IBM’s official security advisories closely for the release of patches or updates addressing CVE-2025-2533 and apply them promptly. 2) Implement strict access controls and network segmentation to limit which users and systems can send queries to the Db2 server, reducing the attack surface. 3) Employ query validation and input filtering mechanisms to detect and block suspicious or malformed queries that could trigger excessive memory allocation. 4) Monitor database server resource usage and set thresholds to alert on abnormal memory consumption patterns that may indicate exploitation attempts. 5) Conduct regular security assessments and penetration testing focused on database query handling to identify potential exploitation vectors. 6) Prepare incident response plans specifically for database availability incidents to minimize downtime and recovery time in case of exploitation. 7) Consider deploying Web Application Firewalls (WAFs) or database activity monitoring tools capable of detecting anomalous query behavior. These measures go beyond generic advice by focusing on proactive detection, access restriction, and rapid response tailored to the nature of this vulnerability.

Description

IBM Db2 for Linux 12.1.0, 12.1.1, and 12.1.2 is vulnerable to a denial of service as the server may crash under certain conditions with a specially crafted query.

References

Community reviews

Loading reviews…