CVE-2026-35096: KTM System e-BOK · Cross-Site Request Forgery (CSRF)
Affects KTM System e-BOKSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 06.2026 when convenient.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 06.2026
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade KTM System e-BOK to 06.2026.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| KTM Systeme-BOK | Affected
| Fixed in
|
AI-suggested
A patch addressing this vulnerability was released in June 2026. Users and administrators should apply the official patch to remediate the issue. Since the vendor advisory or patch links are not explicitly provided, verify and obtain the patch from the official KTM System channels. No alternative mitigations or temporary fixes are indicated.
Description
KTM System e-BOK is vulnerable to Cross‑Site Request Forgery (CSRF) in both the email-change and password-change functionalities. An attacker can craft a malicious website that, when visited by an authenticated user, automatically sends a forged POST request to the application. This allows the attacker to trigger an unauthorized email or password change on behalf of the victim without their knowledge or interaction. This issue was fixed in the patch published in June 2026.