Session hijacking via unrotated client-set identifier
Published Jun 30, 2026 · Updated Jun 30, 2026
Session fixation in KTM System e-BOK before 06.2026 allows attackers to hijack an authenticated session through a fixed cookie. The application accepts a client-supplied session identifier before login and leaves its value unchanged after successful authentication. Exploitation requires planting a known cookie in the victim's browser and the victim logging in, after which the attacker can assume that authenticated session.
Summary
What happened
Session fixation in KTM System e-BOK before 06.2026 allows attackers to hijack an authenticated session through a fixed cookie. The application accepts a client-supplied session identifier before login and leaves its value unchanged after successful authentication. Exploitation requires planting a known cookie in the victim's browser and the victim logging in, after which the attacker can assume that authenticated session.
The record
- CVE
- CVE-2026-35095
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- KTM System
- Product
- e-BOK
- Classifications
- CWE-384, T1550.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 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=0 <06.2026
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