Session data tampering via weak HMAC secret
Published Aug 5, 2026 · Updated Aug 5, 2026
Weak session signing in IBM Maximo Application Suite 9.0, 9.1, and 9.2 allows remote attackers to tamper with session data. The suite signs session data with a weak HMAC secret, so untrusted values are not protected by a sufficiently strong message-authentication key. No authentication or user interaction is required; IBM has not disclosed how the secret is generated or stored, and the documented consequence is limited to session-data integrity.
Summary
What happened
Weak session signing in IBM Maximo Application Suite 9.0, 9.1, and 9.2 allows remote attackers to tamper with session data. The suite signs session data with a weak HMAC secret, so untrusted values are not protected by a sufficiently strong message-authentication key. No authentication or user interaction is required; IBM has not disclosed how the secret is generated or stored, and the documented consequence is limited to session-data integrity.
The record
- CVE
- CVE-2026-18531
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- IBM
- Product
- Maximo Application Suite
- Classifications
- CWE-330, T1606.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=9.0
- Affected versionversion=9.1
- Affected versionversion=9.2
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.
Weakness, pattern, technique
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