Skip to main content
VulnerabilityPublished Updated

CVE-2025-33109: IBM · Execution with Unnecessary Privileges

Affects IBMSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IBMAffected
  • 7.2 – 7.6
5 affected builds
Fixed in–

AI-suggested

  1. Monitor IBM's official security advisories closely and apply patches promptly once released to address CVE-2025-33109.
  2. Until patches are available, restrict access to database procedures and functions to only trusted and necessary accounts, enforcing the principle of least privilege rigorously.
  3. Implement enhanced logging and monitoring of database procedure executions to detect anomalous or unauthorized activity early.
  4. Use network segmentation and firewall rules to limit exposure of IBM i systems to untrusted networks, reducing attack surface.
  5. Conduct regular audits of database permissions and review user roles to ensure no excessive privileges are granted.
  6. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect suspicious database activity patterns.
  7. Educate administrators and security teams about this vulnerability to increase awareness and readiness for incident response.
  8. Consider temporary compensating controls such as disabling non-essential database procedures or functions that could be exploited.

Description

IBM i 7.2, 7.3, 7.4, 7.5, and 7.6 is vulnerable to a privilege escalation caused by an invalid database authority check. A bad actor could execute a database procedure or function without having all required permissions, in addition to causing denial of service for some database actions.

References

Community reviews

Loading reviews…