Cyber Resilience

CVE-2025-36326

Exposed Creds in Ibm Cognos Controller 11.0.0 – 11.0.1

Published
26 September 2025
Modified
03 October 2025
Patch / advisory
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0021 12th percentile
Risk Priority 15 floored blend · peak EPSS

Summary

CVE-2025-36326 is a low-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability in Ibm Cognos Controller. Its CVSS base score is 3.7 (Low).

Operationally, ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Cognos Controller 11.0.0 through 11.0.1, and IBM Controller 11.1.0 through 11.1.1 could allow an attacker to obtain sensitive information due to the use of hardcoded cryptographic keys for signing session cookies.

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-33111Same product: Ibm Cognos Controller
CVE-2025-36015Same product: Ibm Cognos Controller
CVE-2025-33079Same product: Ibm Cognos Controller
CVE-2025-36102Same product: Ibm Cognos Controller
CVE-2024-40691Same product: Ibm Cognos Controller
CVE-2024-25019Same product: Ibm Cognos Controller
CVE-2024-41778Same product: Ibm Controller
CVE-2023-23474Same product: Ibm Cognos Controller
CVE-2024-25035Same product: Ibm Cognos Controller
CVE-2024-25020Same product: Ibm Cognos Controller

Affected Assets

ibm
cognos controller
11.0.0 — 11.0.1
ibm
controller
11.1.0 — 11.1.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-12 Cryptographic Key Establishment and Management
  • SC-23 Session Authenticity
  • IA-5 Authenticator Management
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires proper cryptographic key establishment and management, eliminating the hardcoded keys used to sign session cookies in this CVE.

prevent

Mandates mechanisms that protect session authenticity, preventing forgery or replay of session cookies signed with static keys.

prevent

Requires secure generation, storage, and rotation of authenticators, which would preclude embedding static cryptographic keys for cookie signing.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-SDLC activities such as code review and secret scanning directly prevent embedding static keys.

PR.DS-01 partial match
prevents

Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.

PR.DS-02 partial match
prevents

Data-in-transit protection similarly depends on non-hard-coded keys for encryption.

PR.PS-01 partial match
prevents

Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.

References