Session forgery via hard-coded signing key
Published Aug 13, 2026 · Updated Aug 13, 2026
Hard-coded cryptographic key use in IBM Documentation Offline 1.0.0 through 1.4.1 allows remote attackers to forge session tokens. The embedded Node.js server uses a default hard-coded session secret to validate tokens, so tokens signed with that shared secret are accepted. Exploitation requires network access to the embedded service and permits manipulation of client-side session state, with no direct data-read or code-execution impact reported for this CVE.
Summary
What happened
Hard-coded cryptographic key use in IBM Documentation Offline 1.0.0 through 1.4.1 allows remote attackers to forge session tokens. The embedded Node.js server uses a default hard-coded session secret to validate tokens, so tokens signed with that shared secret are accepted. Exploitation requires network access to the embedded service and permits manipulation of client-side session state, with no direct data-read or code-execution impact reported for this CVE.
The record
- CVE
- CVE-2026-17468
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- IBM
- Product
- IBM Documentation Offline
- Classifications
- CWE-321, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <=1.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo