CVE-2025-36062
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 Cognos Analytics Mobile (iOS) 1.1.0 through 1.1.22 could be vulnerable to information exposure due to the use of unencrypted network traffic.
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 confidenceIBM Cognos Analytics Mobile for iOS versions 1.1.0 through 1.1.22 transmits data over unencrypted network connections, allowing attackers on the same network to intercept sensitive business data, authentication credentials, and analytics content via man-in-the-middle attacks.
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>= 1.1.0, < 1.1.23CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate IBM Cognos Analytics Mobile on the iOS deviceOpen the iOS Settings app, scroll down to find the list of installed apps, and tap on 'IBM Cognos Analytics Mobile' in the Applications sectionAffected if The app is installed on the device
-
Identify the installed version numberIn the IBM Cognos Analytics Mobile app settings screen, locate the 'Version' or 'Version Info' field which displays the current app version (for example: 1.1.0, 1.1.15, 1.1.22)Affected if The displayed version is unknown or cannot be determined
-
Compare version against the affected rangeReview the version number shown and compare it to the affected range: versions 1.1.0 through 1.1.22 are vulnerable; version 1.1.23 and later are patchedAffected if The installed version is 1.1.22 or lower (any version from 1.1.0 up to and including 1.1.22)
-
Verify the app version via App Store if availableOpen the Apple App Store, search for 'IBM Cognos Analytics Mobile', tap on the app, and review the version number in the app description to confirm the latest available versionAffected if The installed version is lower than the version shown in the App Store, particularly if the App Store shows 1.1.23 or later
The user is affected if the installed IBM Cognos Analytics Mobile iOS app version is 1.1.22 or lower, since these versions transmit data over unencrypted network connections.
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 · scoped1.1.23
Update to IBM Cognos Analytics Mobile iOS version 1.1.23 or later which implements TLS encryption for all network communications, or configure the app to exclusively use HTTPS endpoints.
1.1.23 or later
- Upgrade IBM Cognos Analytics Mobile for iOS to version 1.1.23 or later
- The upgrade can be obtained through the Apple App Store
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36062 — 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-36062 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