dbcve.org
Tivoli Netcool\/impactApplication · Ibm

CVE-2026-4788

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 7.1.0.38 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Tivoli Netcool Impact 7.1.0.0 through 7.1.0.37 stores sensitive information in log files that could be read by a local user.

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 Tivoli Netcool Impact versions 7.1.0.0 through 7.1.0.37 contains a vulnerability where sensitive information is written to log files with insufficient access controls, allowing any local user to read potentially confidential data such as credentials, tokens, or other secrets that may be logged during operation.

MitigationUpgrade to IBM Tivoli Netcool Impact 7.1.0.38 or later, or implement strict file permissions on log directories to prevent unauthorized local user access to log files containing sensitive data.

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
Tivoli Netcool\/impactApplication
Affected:>= 7.1.0.0, < 7.1.0.38

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

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Identify the installed IBM Tivoli Netcool Impact version
    Run the command 'impact -version' or check the installation directory for version metadata files, typically found in the Impact home directory or via the impactcmd utility.
    Affected if The installed version falls within 7.1.0.0 through 7.1.0.37 inclusive.
  2. Confirm the product is deployed and generating logs
    Locate the Netcool Impact log directory. Default paths typically include $IMPACT_HOME/logs or /opt/IBM/Netcool/Impact/logs. Verify log files exist and are actively being written to.
    Affected if Log files exist and the product is running, creating an opportunity for unauthorized access to sensitive data in logs.
  3. Examine log files for sensitive information exposure
    Use a text search tool (grep, strings, or a text editor) to inspect recent log files for patterns that may indicate sensitive data such as passwords, credentials, tokens, or personal identifiable information. Look for keywords like 'password', 'secret', 'key', or 'credential'.
    Affected if Sensitive data such as passwords, authentication tokens, or confidential parameters appear in plain text within log files.
  4. Review file permissions on log directories and files
    Run 'ls -la' on the log directory path and examine the ownership and permission bits. Check whether the log files are readable by users other than the impact service account.
    Affected if Log files or directories have overly permissive access (e.g., world-readable permissions or readable by non-admin users), allowing local users to read sensitive log contents.

You are affected if the installed version is 7.1.0.0 through 7.1.0.37 and log files are present with either sensitive data visible or permissive file permissions enabling unauthorized access.

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

Upgrade to IBM Tivoli Netcool Impact 7.1.0.38 or later, or implement strict file permissions on log directories to prevent unauthorized local user access to log files containing sensitive data.

Recommended fix Moderate confidence

7.1.0.38

  1. 1. Back up the current IBM Tivoli Netcool/Impact installation, including all configuration files and databases
  2. 2. Access IBM Fix Central (https://www.ibm.com/support/fixcentral) or the IBM Passport Advantage site
  3. 3. Download IBM Tivoli Netcool/Impact version 7.1.0.38 or later
  4. 4. Stop all Netcool/Impact services to ensure a clean upgrade environment
  5. 5. Install the upgraded version (7.1.0.38 or later) following the IBM installation documentation
  6. 6. Verify that the sensitive information logging issue is resolved by reviewing log file contents
  7. 7. Restart Netcool/Impact services and confirm normal operation

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

Fix this in Tivoli Netcool\/impact Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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