CVE-2026-14963
IBM Cognos Command Center has addressed vulnerabilities
IBM Cognos Command Center 10.2.4.1 and 10.2.5 could allow a remote attacker to execute unauthorized processes due to cross-site request forgery.
Fixes and workarounds
Fix
IBM strongly recommends addressing the vulnerability now by upgrading. Affected Product(s)VersionFixIBM Cognos Command Center10.2.5 - 10.2.5 FP1 IF4 IBM® Cognos® Command Center® 10.2.5 FP1 IF5 available for download https://www.ibm.com/support/pages/node/7289948 IBM Cognos Command Center10.2.4.1 - 10.2.4.1 IF19 IBM® Cognos® Command Center® 10.2.5 FP1 IF5 available for download https://www.ibm.com/support/pages/node/7289948 IBM Cognos Command Center Cloud environments have been updated.
Source: CNA: ibmFix
The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.
Source: CNA: ibmAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Cognos Command Center IBM |
10.2.4.1 (affected) 10.2.5 (affected) |
CNA: ibm |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 4.3 medium |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N | CNA: ibm |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://www.ibm.com/support/pages/node/7290010CNA: ibm · vendor-advisory, patch
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.