CVE-2025-36015
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 · uneditedIBM 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.
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 confidenceIBM Controller 11.1.0-11.1.1 and Cognos Controller 11.0.0-11.0.1 FP6 contain a DoS vulnerability where authenticated users can trigger a denial of service by providing improperly validated quantity size input, likely causing the application to crash or become unresponsive.
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>= 11.0.0, < 11.0.1.7>= 11.1.0, < 11.1.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed product and versionCheck the IBM Controller or Cognos Controller installation. This is typically found in the program's 'About' section, in the installation directory's version file, or by querying the application through its administration interface. Common locations include the 'about' dialog in the software or registry entries under HKLM\Software\IBM\Cognos\Controller (Windows).Affected if The installed version is IBM Controller 11.1.0 through 11.1.1, or IBM Cognos Controller 11.0.0 through 11.0.1.6 (versions before 11.0.1.7).
-
Confirm the product typeDetermine whether the installation is IBM Controller or IBM Cognos Controller. These are distinct products with different version numbering. Check the product name in the installation or program information.Affected if The product is either IBM Controller in the 11.1.0-11.1.1 range or IBM Cognos Controller in the 11.0.0-11.0.1.6 range.
-
Verify user authentication is enabledCheck that the application has user authentication configured and active. This vulnerability requires an authenticated user to trigger the improperly validated quantity size input. Verify through the application security settings or user management console.Affected if The application allows authenticated users to access features that process quantity size inputs.
You are affected if IBM Controller version is 11.1.0-11.1.1 or IBM Cognos Controller version is 11.0.0-11.0.1.6 and the application accepts authenticated user input for quantity size fields.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped11.0.1.711.1.2
Implement robust server-side validation for quantity size inputs to ensure values are within acceptable bounds and of the correct data type before processing.
IBM Cognos Controller 11.0.1.7 or IBM Controller 11.1.2
- 1. Back up the IBM Cognos Controller or Controller database and configuration files
- 2. Ensure you have valid IBM Cognos Controller maintenance coverage
- 3. Download the appropriate fixed version from IBM Fix Central (11.0.1.7 for Cognos Controller or 11.1.2 for Controller)
- 4. Stop all IBM Cognos Controller services
- 5. Install the upgrade following IBM's installation documentation
- 6. Verify the upgrade by checking the version in About IBM Cognos Controller
- 7. Restart the services and test that the application functions normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-36015 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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