PatchSiren cyber security CVE debrief
CVE-2026-17473 IBM CVE debrief
IBM Documentation Offline 1.0.0 through 1.4.1 could allow a remote attacker to read arbitrary files due to improper limitation of a pathname to a restricted directory. This vulnerability exists in the IBM Documentation Offline product, which is susceptible to a directory traversal attack. A remote attacker could exploit this vulnerability to read arbitrary files, potentially leading to sensitive information disclosure. The affected versions of IBM Documentation Offline should be reviewed, and vendor-provided patches or updates should be applied to mitigate the risk.
- Vendor
- IBM
- Product
- Documentation Offline
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-13
- Original CVE updated
- 2026-08-25
- Advisory published
- 2026-08-13
- Advisory updated
- 2026-08-25
Who should care
IBM Documentation Offline users and administrators, as well as security teams and vulnerability management teams, should be aware of this vulnerability and take necessary precautions to mitigate the risk. This includes reviewing the affected versions of IBM Documentation Offline, checking for vendor-provided patches or updates, and implementing compensating controls to restrict access to the affected system or monitor for suspicious activity. Additionally, operators and platform administrators should be informed about the potential impact of this vulnerability on their systems and take appropriate measures to ensure the security of their environments. Security teams should also prioritize remediation efforts and conduct inventory checks to identify potentially vulnerable systems.
Technical summary
The vulnerability exists due to improper limitation of a pathname to a restricted directory in IBM Documentation Offline 1.0.0 through 1.4.1. A remote attacker could exploit this vulnerability to read arbitrary files by sending a specially crafted request to the affected system. The vulnerability is considered high-severity due to its potential impact on the confidentiality of sensitive information. IBM Documentation Offline users and administrators should review the affected versions and apply vendor-provided patches or updates to prevent exploitation.
Defensive priority
High-priority defensive actions are recommended due to the high CVSS score of 7.5 and the potential for remote attackers to read arbitrary files.
Recommended defensive actions
- Verify the affected versions of IBM Documentation Offline and check for vendor-provided patches or updates.
- Implement compensating controls, such as restricting access to the affected system or monitoring for suspicious activity.
- Conduct inventory checks to identify potentially vulnerable systems and prioritize remediation efforts.
Evidence notes
The CVE record and NVD detail provide information on the vulnerability, but further verification is needed to confirm the affected scope and vendor remediation. Additional review of vendor documentation and security advisories is recommended to ensure accurate understanding of the vulnerability and its potential impact. It is also essential to verify the affected versions of IBM Documentation Offline and check for vendor-provided patches or updates.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-17473 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-17473
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-17473 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-17473
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://www.ibm.com/support/pages/node/7283484
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.