CVE-2026-35096
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKTM 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceKTM System e-BOK is vulnerable to Cross-Site Request Forgery (CSRF) in the email-change and password-change functionalities. The application lacks proper anti-CSRF protection, allowing authenticated users to have their requests forged when visiting malicious websites. An attacker can craft a forged POST request that the victim's browser will automatically send, enabling unauthorized modification of email or password without the user's knowledge.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Inspect email change request for CSRF tokenCapture a legitimate email change request (POST to the email change endpoint) using browser DevTools or a proxy. Examine the request headers and body for a CSRF token, anti-CSRF token, or similar security token parameter.Affected if No CSRF token or token parameter is present in the email change request
-
Inspect password change request for CSRF tokenCapture a legitimate password change request (POST to the password change endpoint) using browser DevTools or a proxy. Examine the request headers and body for a CSRF token, anti-CSRF token, or similar security token parameter.Affected if No CSRF token or token parameter is present in the password change request
-
Verify SameSite cookie attribute on session cookiesOpen the browser DevTools Application/Storage tab and examine the session cookies set by the e-BOK application. Check if the SameSite attribute is present and set to 'Lax' or 'Strict'.Affected if Session cookies lack a SameSite attribute or have SameSite=None without the Secure flag
-
Test CSRF vulnerability with a forged requestWhile authenticated to e-BOK, send a crafted POST request to the email or password change endpoint from a different origin (such as via curl or Burp Repeater) without including any CSRF token. Observe if the action succeeds.Affected if The forged request succeeds without requiring a valid CSRF token
The environment is affected if email change and password change endpoints lack CSRF tokens and session cookies lack proper SameSite attributes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing operations including email and password changes, and configure SameSite attributes on session cookies to prevent cross-origin request transmission.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data