Cognos Analytics
IBM- Product type
- Other
- Catalog vulnerabilities
- 98
Severity across 98 analyzed records
en
Verify to analyze this security profile
As of 09/13/2026, within CyStack's analyzed data, Cognos Analytics has 1 security vulnerability published in the last 90 days. Of these, 0 are rated High or Critical. None of these vulnerabilities is listed in the CISA KEV catalog. CyStack recommends that organizations and individual users remediate applicable vulnerabilities as soon as possible.
CyStack does not yet have sufficient official-source data to identify the latest version of Cognos Analytics and determine which vulnerabilities affect that version.
| Vulnerability | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-15995IBM Cognos Analytics 12.1.3 general availability package contains a data integrity issue in the Agentic AI assistant that may cause incorrect report summaries or report-processing errors under concurrent use | Exploitation statusNot known exploited | FixYes | Published07/17/2026 | SeverityMedium |
CVE-2025-3633IBM Cognos Analytics is affected by multiple security vulnerabilities | Exploitation statusNot known exploited | FixYes | Published05/27/2026 | SeverityMedium |
CVE-2025-36126IBM Cognos Analytics is affected by Cross-site scripting. | Exploitation statusNot known exploited | FixYes | Published05/26/2026 | SeverityMedium |
CVE-2024-52900IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixYes | Published06/28/2025 | SeverityMedium |
CVE-2025-0923IBM Cognos Analytics information disclosure | Exploitation statusNot known exploited | FixYes | Published06/11/2025 | SeverityMedium |
CVE-2025-0917IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixYes | Published06/11/2025 | SeverityMedium |
CVE-2025-25032IBM Cognos Analytics denial of service | Exploitation statusNot known exploited | FixYes | Published06/11/2025 | SeverityHigh |
CVE-2024-56340IBM Cognos Analytics path traversal | Exploitation statusNot known exploited | FixYes | Published02/28/2025 | SeverityMedium |
CVE-2025-0823IBM MQ path traversal | Exploitation statusNot known exploited | FixYes | Published02/28/2025 | SeverityMedium |
CVE-2024-49352IBM Cognos Anaytics XML external entity injection | Exploitation statusNot known exploited | FixNot confirmed | Published02/05/2025 | SeverityHigh |
CVE-2024-40695IBM Cognos Analytics file upload | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityHigh |
CVE-2024-51466IBM Cognos Analytics expression language injection | Exploitation statusNot known exploited | FixYes | Published12/20/2024 | SeverityCritical |
CVE-2024-25042IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixYes | Published12/18/2024 | SeverityMedium |
CVE-2024-45082IBM Cognos Analytics HTTP open redirection | Exploitation statusNot known exploited | FixYes | Published12/18/2024 | SeverityMedium |
CVE-2024-41752IBM Cognos Analytics HTML injection | Exploitation statusNot known exploited | FixYes | Published12/18/2024 | SeverityMedium |
CVE-2024-40703IBM Cognos Analytics information disclosure | Exploitation statusNot known exploited | FixNot confirmed | Published09/22/2024 | SeverityMedium |
CVE-2024-25041IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixNot confirmed | Published06/28/2024 | SeverityMedium |
CVE-2024-25053IBM Cognos Analytics improper certificate validation | Exploitation statusNot known exploited | FixNot confirmed | Published06/28/2024 | SeverityMedium |
CVE-2024-25047IBM Cognos Analytics log injection | Exploitation statusNot known exploited | FixNot confirmed | Published05/02/2024 | SeverityHigh |
CVE-2023-43051IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixNot confirmed | Published02/24/2024 | SeverityMedium |
CVE-2022-34357IBM Cognos Analytics Mobile Server denial of service | Exploitation statusNot known exploited | FixNot confirmed | Published02/24/2024 | SeverityMedium |
CVE-2023-30996IBM Cognos Analytics cross-origin resource sharing | Exploitation statusNot known exploited | FixNot confirmed | Published02/24/2024 | SeverityMedium |
CVE-2023-32344IBM Cognos Analytics cross-site request forgery | Exploitation statusNot known exploited | FixNot confirmed | Published02/24/2024 | SeverityMedium |
CVE-2023-38359IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixNot confirmed | Published02/24/2024 | SeverityMedium |
CVE-2023-35011IBM Cognos Analytics server-side request forgey | Exploitation statusNot known exploited | FixNot confirmed | Published08/16/2023 | SeverityMedium |
CVE-2023-35009IBM Cognos Analytics information disclosure | Exploitation statusNot known exploited | FixNot confirmed | Published08/16/2023 | SeverityMedium |
CVE-2023-28530IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixNot confirmed | Published07/22/2023 | SeverityMedium |
CVE-2023-25929IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixNot confirmed | Published07/22/2023 | SeverityMedium |
CVE-2021-39036IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixNot confirmed | Published05/12/2023 | SeverityMedium |
CVE-2022-39160IBM Cognos Analytics cross-site scripting | Exploitation statusNot known exploited | FixNot confirmed | Published12/19/2022 | SeverityMedium |
CVE-2022-43883IBM Cognos Analytics data manipulation | Exploitation statusNot known exploited | FixNot confirmed | Published12/19/2022 | SeverityMedium |
CVE-2022-43887IBM Cognos Analytics information disclosure | Exploitation statusNot known exploited | FixNot confirmed | Published12/19/2022 | SeverityMedium |
CVE-2022-38708IBM Cognos Analytics server-side request forgery | Exploitation statusNot known exploited | FixNot confirmed | Published12/19/2022 | SeverityMedium |
CVE-2022-36773 | Exploitation statusNot confirmed | FixNot confirmed | Published09/01/2022 | SeverityHigh |
CVE-2022-30614 | Exploitation statusNot confirmed | FixNot confirmed | Published09/01/2022 | SeverityMedium |
CVE-2021-39045 | Exploitation statusNot confirmed | FixNot confirmed | Published09/01/2022 | SeverityMedium |
CVE-2021-39009 | Exploitation statusNot confirmed | FixNot confirmed | Published09/01/2022 | SeverityMedium |
CVE-2021-29823 | Exploitation statusNot confirmed | FixNot confirmed | Published09/01/2022 | SeverityMedium |
CVE-2021-20468 | Exploitation statusNot confirmed | FixNot confirmed | Published09/01/2022 | SeverityMedium |
CVE-2020-4301 | Exploitation statusNot confirmed | FixNot confirmed | Published09/01/2022 | SeverityMedium |
CVE-2021-39047 | Exploitation statusNot confirmed | FixNot confirmed | Published06/24/2022 | SeverityMedium |
CVE-2021-38945 | Exploitation statusNot confirmed | FixNot confirmed | Published06/24/2022 | SeverityMedium |
CVE-2021-29768 | Exploitation statusNot confirmed | FixNot confirmed | Published06/24/2022 | SeverityMedium |
CVE-2021-38946 | Exploitation statusNot confirmed | FixNot confirmed | Published04/22/2022 | SeverityMedium |
CVE-2021-38905 | Exploitation statusNot confirmed | FixNot confirmed | Published04/22/2022 | SeverityMedium |
CVE-2021-38904 | Exploitation statusNot confirmed | FixNot confirmed | Published04/22/2022 | SeverityMedium |
CVE-2021-38903 | Exploitation statusNot confirmed | FixNot confirmed | Published04/22/2022 | SeverityMedium |
CVE-2021-38886 | Exploitation statusNot confirmed | FixNot confirmed | Published04/22/2022 | SeverityMedium |
CVE-2021-29824 | Exploitation statusNot confirmed | FixNot confirmed | Published04/22/2022 | SeverityLow |
CVE-2021-20464 | Exploitation statusNot confirmed | FixNot confirmed | Published04/22/2022 | SeverityMedium |
CVE-2021-38909 | Exploitation statusNot confirmed | FixNot confirmed | Published12/03/2021 | SeverityMedium |
CVE-2021-29867 | Exploitation statusNot confirmed | FixNot confirmed | Published12/03/2021 | SeverityMedium |
CVE-2021-29756 | Exploitation statusNot confirmed | FixNot confirmed | Published12/03/2021 | SeverityMedium |
CVE-2021-29719 | Exploitation statusNot confirmed | FixNot confirmed | Published12/03/2021 | SeverityMedium |
CVE-2021-29716 | Exploitation statusNot confirmed | FixNot confirmed | Published12/03/2021 | SeverityLow |
CVE-2021-20493 | Exploitation statusNot confirmed | FixNot confirmed | Published12/03/2021 | SeverityMedium |
CVE-2021-20470 | Exploitation statusNot confirmed | FixNot confirmed | Published12/03/2021 | SeverityMedium |
CVE-2021-29745 | Exploitation statusNot confirmed | FixNot confirmed | Published10/15/2021 | SeverityMedium |
CVE-2021-29679 | Exploitation statusNot confirmed | FixNot confirmed | Published10/15/2021 | SeverityHigh |
CVE-2020-4951 | Exploitation statusNot confirmed | FixNot confirmed | Published10/15/2021 | SeverityMedium |
CVE-2021-20461 | Exploitation statusNot confirmed | FixNot confirmed | Published06/30/2021 | SeverityMedium |
CVE-2020-4561 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityCritical |
CVE-2020-4520 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityHigh |
CVE-2020-4354 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityMedium |
CVE-2020-4300 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityHigh |
CVE-2019-4730 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityHigh |
CVE-2019-4724 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityMedium |
CVE-2019-4723 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityMedium |
CVE-2019-4722 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityMedium |
CVE-2019-4653 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityMedium |
CVE-2019-4471 | Exploitation statusNot confirmed | FixNot confirmed | Published05/31/2021 | SeverityMedium |
CVE-2020-4388 | Exploitation statusNot confirmed | FixNot confirmed | Published10/12/2020 | SeverityMedium |
CVE-2020-4302 | Exploitation statusNot confirmed | FixNot confirmed | Published10/12/2020 | SeverityMedium |
CVE-2020-4377 | Exploitation statusNot confirmed | FixNot confirmed | Published08/03/2020 | SeverityHigh |
CVE-2019-4589 | Exploitation statusNot confirmed | FixNot confirmed | Published08/03/2020 | SeverityMedium |
CVE-2019-4366 | Exploitation statusNot confirmed | FixNot confirmed | Published08/03/2020 | SeverityLow |
CVE-2019-4729 | Exploitation statusNot confirmed | FixNot confirmed | Published04/27/2020 | SeverityMedium |
CVE-2019-4623 | Exploitation statusNot confirmed | FixNot confirmed | Published12/30/2019 | SeverityMedium |
CVE-2019-4343 | Exploitation statusNot confirmed | FixNot confirmed | Published12/30/2019 | SeverityMedium |
CVE-2019-4555 | Exploitation statusNot confirmed | FixNot confirmed | Published12/20/2019 | SeverityMedium |
CVE-2019-4231 | Exploitation statusNot confirmed | FixNot confirmed | Published12/20/2019 | SeverityMedium |
CVE-2019-4645 | Exploitation statusNot confirmed | FixNot confirmed | Published11/09/2019 | SeverityMedium |
CVE-2019-4334 | Exploitation statusNot confirmed | FixNot confirmed | Published11/09/2019 | SeverityMedium |
CVE-2018-1721 | Exploitation statusNot confirmed | FixNot confirmed | Published11/09/2019 | SeverityHigh |
CVE-2019-4342 | Exploitation statusNot confirmed | FixNot confirmed | Published09/17/2019 | SeverityMedium |
CVE-2019-4183 | Exploitation statusNot confirmed | FixNot confirmed | Published09/17/2019 | SeverityMedium |
CVE-2019-4139 | Exploitation statusNot confirmed | FixNot confirmed | Published05/29/2019 | SeverityMedium |
CVE-2019-4178 | Exploitation statusNot confirmed | FixNot confirmed | Published04/15/2019 | SeverityMedium |
CVE-2018-1842 | Exploitation statusNot confirmed | FixNot confirmed | Published11/09/2018 | SeverityLow |
CVE-2018-1413 | Exploitation statusNot confirmed | FixNot confirmed | Published05/07/2018 | SeverityUnknown |
CVE-2016-9711 | Exploitation statusNot confirmed | FixNot confirmed | Published03/22/2018 | SeverityMedium |
CVE-2017-1783 | Exploitation statusNot confirmed | FixNot confirmed | Published01/29/2018 | SeverityUnknown |
CVE-2017-1779 | Exploitation statusNot confirmed | FixNot confirmed | Published01/29/2018 | SeverityUnknown |
CVE-2017-1784 | Exploitation statusNot confirmed | FixNot confirmed | Published01/29/2018 | SeverityUnknown |
CVE-2017-1485 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2017 | SeverityUnknown |
CVE-2017-1427 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2017 | SeverityUnknown |
CVE-2017-1428 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2017 | SeverityUnknown |
CVE-2017-1535 | Exploitation statusNot confirmed | FixNot confirmed | Published08/29/2017 | SeverityUnknown |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan