dbcve.org
Analytics Content HubApplication · Ibm

CVE-2025-36090

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-10
Fix available
A fix is available. Upgrade to 2.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Analytics Content Hub 2.0, 2.1, 2.2, and 2.3 could allow a remote attacker to obtain information about the application framework which could be used in reconnaissance to gather information for future attacks from a detailed technical error message.

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

IBM Analytics Content Hub versions 2.0-2.3 exposes detailed technical error messages that reveal information about the application framework. An unauthenticated remote attacker can trigger these error messages during reconnaissance to learn about the underlying technology stack, potentially identifying specific vulnerabilities associated with those components.

MitigationConfigure custom error pages that display generic messages to users while logging detailed errors server-side only. Review and disable verbose error reporting in the application framework configuration.

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
Analytics Content HubApplication
Affected:>= 2.0, < 2.4

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

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

  1. Determine installed IBM Analytics Content Hub version
    Locate and inspect the version information for your IBM Analytics Content Hub installation (typically available in the product UI under About, or via administrative console)
    Affected if The installed version is 2.0, 2.1, 2.2, or 2.3 (any version >= 2.0 and < 2.4)
  2. Check if custom error pages are configured
    Review the application server or web container configuration for custom error page mappings (look for custom error or error-page directives in configuration files)
    Affected if Custom error pages are NOT configured - the application displays framework-level error messages instead of generic pages
  3. Check verbose error reporting setting
    Inspect the application framework configuration for verbose error reporting, stack trace display, or debug mode settings
    Affected if Verbose error reporting or debug mode is enabled, causing detailed exception information to be returned in HTTP responses
  4. Trigger a test error to observe response
    Send a malformed request or access a non-existent resource to intentionally trigger an error condition, then inspect the HTTP response body
    Affected if The response contains technical details such as framework names, version numbers, stack traces, or internal file paths

You are affected if your IBM Analytics Content Hub version is 2.0-2.3 AND verbose error reporting is enabled or custom error pages are not configured, causing detailed technical information to be exposed in error responses.

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 2.4 or later
Fixed in 2.4
Interim mitigation

Configure custom error pages that display generic messages to users while logging detailed errors server-side only. Review and disable verbose error reporting in the application framework configuration.

Recommended fix Moderate confidence

IBM Analytics Content Hub 2.4 or later

  1. Upgrade IBM Analytics Content Hub to version 2.4 or later to remediate the information disclosure vulnerability.
  2. After upgrading, verify that detailed technical error messages are no longer exposed to remote attackers.
  3. Confirm the application is functioning correctly post-upgrade.

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

Fix this in Analytics Content Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36090 — 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-36090 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