Skip to main content
VulnerabilityPublished

CVE-2025-36015: IBM Controller · Improper Validation of Specified Quantity in Input

Affects IBM ControllerSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% 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:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

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

What to do

Affected software

ProductAffectedFixed in
Mavencom.ibm/controllerpkg:maven/com.ibm/controllerOther threatsAffected
  • =11.1.0
Fixed in–

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

AI-suggested

  1. Apply official IBM patches or updates as soon as they become available to address the input validation flaw directly.
  2. Until patches are released, restrict user privileges to the minimum necessary, limiting authenticated users who can submit quantity inputs.
  3. Implement strict input validation and sanitization at the application or network layer to detect and block anomalous or oversized quantity inputs.
  4. Monitor system logs and application behavior for unusual input patterns or repeated failed attempts that could indicate exploitation attempts.
  5. Employ network segmentation and access controls to limit exposure of IBM Controller systems to only trusted internal users.
  6. Conduct regular credential audits and enforce strong authentication mechanisms to reduce risk from compromised accounts.
  7. Prepare incident response plans specifically addressing potential DoS scenarios affecting IBM Controller to minimize downtime.
  8. Engage with IBM support and subscribe to security advisories for timely updates and guidance.

Description

IBM Controller 11.1.0 through 11.1.1 and IBM Cognos Controller 11.0.0 through 11.0.1 FP6 could allow an authenticated user to cause a denial of service due to improper validation of a specified quantity size input.

References

Community reviews

Loading reviews…