dbcve.org
Cognos Analytics MobileApplication · Ibm

CVE-2025-36106

HIGH · 8.2 CVSS v3.1 Published 2025-07-21
Fix available
A fix is available. Upgrade to 1.1.23 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
IBM Cognos Analytics Mobile (iOS) 1.1.0 through 1.1.22 could allow malicious actors to view and modify information coming to and from the application which could then be used to access confidential information on the device or network by using a the deprecated or misconfigured AFNetworking library at runtime.

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 · high confidence

IBM Cognos Analytics Mobile (iOS) versions 1.1.0 through 1.1.22 uses a deprecated and misconfigured AFNetworking library that lacks proper SSL certificate pinning, allowing man-in-the-middle attacks. This enables attackers to intercept, view, and modify encrypted network traffic between the application and backend servers.

MitigationUpgrade to a newer version of IBM Cognos Analytics Mobile that replaces the deprecated AFNetworking library with a current, properly configured networking library with SSL pinning enabled, or apply vendor-supplied patches.

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
Cognos Analytics MobileApplication
Affected:>= 1.1.0, < 1.1.23

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed version of IBM Cognos Analytics Mobile
    Open the App Store or your device's app settings to view the installed version number. Compare this version against the affected range: 1.1.0 through 1.1.22
    Affected if The installed version is 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.1.10, 1.1.11, 1.1.12, 1.1.13, 1.1.14, 1.1.15, 1.1.16, 1.1.17, 1.1.18, 1.1.19, 1.1.20, 1.1.21, or 1.1.22
  2. Inspect network traffic for certificate validation
    Use a proxy tool like Burp Suite or Charles Proxy to intercept traffic from the IBM Cognos Analytics Mobile app. Observe whether the app validates server certificates properly or accepts invalid certificates without warning
    Affected if The app accepts connections to the backend without proper SSL/TLS certificate validation, allowing the proxy to intercept traffic without detection
  3. Check if SSL certificate pinning is enforced
    Attempt a man-in-the-middle test by introducing an untrusted certificate. If the app connects successfully without rejecting the invalid certificate, SSL pinning is not properly enabled
    Affected if The app does not reject connections when presented with an invalid or self-signed SSL certificate, indicating certificate pinning is disabled or misconfigured
  4. Verify the AFNetworking library is in use
    If you have access to the application binary or can inspect the app bundle, search for the presence of the AFNetworking library (libAFNetworking.a or AFNetworking.framework) within the application package
    Affected if The application bundle contains the deprecated AFNetworking library, indicating the vulnerable library is still in use

You are affected if the installed version falls within 1.1.0 to 1.1.22 and the app either uses the deprecated AFNetworking library or fails to properly validate SSL certificates, allowing intercepted network traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.1.23 or later
Fixed in 1.1.23
Interim mitigation

Upgrade to a newer version of IBM Cognos Analytics Mobile that replaces the deprecated AFNetworking library with a current, properly configured networking library with SSL pinning enabled, or apply vendor-supplied patches.

Recommended fix High confidence

1.1.23 or later

  1. Update IBM Cognos Analytics Mobile to version 1.1.23 or later via the Apple App Store
  2. Verify the update was successful by checking the app version in the iOS App Store or device settings

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cognos Analytics Mobile Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
40.0 hours of engineering $6,960
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36106 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36106 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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