Unauthorized actions via replayed CSRF tokens
Published Feb 4, 2026 · Updated Feb 4, 2026
Cross-site request forgery in IBM Operations Analytics - Log Analysis 1.3.5.0 through 1.3.8.3 allows attackers to trigger unauthorized actions. The web interface accepts a previously issued CSRF token again instead of enforcing single-use validation for state-changing requests. Exploitation requires a trusted user with an active authenticated session to interact with attacker-controlled content, and resulting actions remain bounded by that user's privileges.
Summary
What happened
Cross-site request forgery in IBM Operations Analytics - Log Analysis 1.3.5.0 through 1.3.8.3 allows attackers to trigger unauthorized actions. The web interface accepts a previously issued CSRF token again instead of enforcing single-use validation for state-changing requests. Exploitation requires a trusted user with an active authenticated session to interact with attacker-controlled content, and resulting actions remain bounded by that user's privileges.
The record
- CVE
- CVE-2024-40685
- Published
- Feb 4, 2026
- Updated
- Feb 4, 2026
- Vendor
- IBM
- Product
- Operations Analytics - Log Analysis
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2026CVE publishedPublication date reported by the CVE source.
- Feb 4, 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.3.5.0 <=1.3.8.3
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