Skip to main content
CVE-2025-14687VulnerabilityPublished

CVE-2025-14687: IBM Db2 Intelligence Center · Client-Side Enforcement of Server-Side Security

Affects IBM Db2 Intelligence CenterSource CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Dec 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-26.

What to do

Affected software

ProductAffectedFixed in
IBM Db2 Intelligence CenterAffected
  • =1.1.0
  • =1.1.1
  • =1.1.2
Fixed in–

AI-suggested

1. Monitor IBM’s security advisories closely and apply official patches or updates as soon as they become available to address CVE-2025-14687. 2. Until patches are released, restrict user privileges to the minimum necessary, especially limiting access to sensitive functions within Db2 Intelligence Center. 3. Implement strict role-based access control (RBAC) and regularly review user permissions to prevent privilege escalation. 4. Employ network segmentation and firewall rules to limit access to the Db2 Intelligence Center to trusted users and systems only. 5. Use application-layer monitoring and logging to detect anomalous or unauthorized actions within the platform, enabling early detection of exploitation attempts. 6. Conduct security awareness training for administrators and users to recognize and report suspicious activities. 7. Consider deploying Web Application Firewalls (WAF) or runtime application self-protection (RASP) solutions that can detect and block client-side manipulation attempts. 8. Review and harden client-side code and configurations where possible to reduce the attack surface related to client-side enforcement flaws.

Description

IBM Db2 Intelligence Center 1.1.0, 1.1.1, 1.1.2 could allow an authenticated user to perform unauthorized actions due to client-side enforcement of sever side security mechanisms.

References

Community reviews

Loading reviews…