CVE-2026-35098
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 does not implement any limit or timeout on consecutive login attempts, allowing an attacker to perform unlimited authentication requests. This lack of rate‑limiting enables efficient brute‑force attacks against user accounts. When combined with vulnerability CVE-2026-35097, where passwords are restricted to a six‑digit numeric format, this becomes a critical issue, as such passwords can be brute‑forced in a relatively short time. 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 · high confidenceKTM System e-BOK lacks rate-limiting and timeout controls on authentication attempts, enabling unlimited consecutive login tries. Combined with the companion vulnerability (CVE-2026-35097) where passwords are restricted to six-digit numeric format, this creates an efficient brute-force attack vector allowing attackers to systematically guess all possible combinations (000000-999999) without detection or throttling.
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
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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.
-
Identify if KTM System e-BOK is exposedReview network exposure of e-BOK authentication interfaces. Check if login endpoints are accessible from untrusted networks or the public internet.Affected if e-BOK login interface is directly accessible from external/untrusted networks without VPN or authentication gateway
-
Verify rate-limiting on login endpointsTest the login endpoint by sending multiple consecutive authentication requests. Observe if any throttling, delays, or blocking occurs after repeated attempts.Affected if No throttling or rate limits are enforced - requests are processed without delay or restriction regardless of attempt frequency
-
Check for account lockout policiesExamine authentication configuration or attempt to trigger account lockout through repeated failed login attempts. Document if accounts remain accessible after many failures.Affected if No account lockout mechanism exists - accounts remain active after unlimited failed login attempts
-
Confirm password complexity policyReview the password policy configuration for the e-BOK system. Check if passwords are restricted to 6-digit numeric format (000000-999999).Affected if Passwords are limited to exactly 6 numeric digits, enabling 1,000,000 possible combinations
-
Review authentication logging and monitoringCheck if login attempt logging, alerting, or brute-force detection mechanisms are in place. Test if excessive failed attempts generate alerts or are logged for review.Affected if No logging, alerting, or detection for excessive failed authentication attempts
If the e-BOK login interface is exposed and lacks rate-limiting, account lockout, and comprehensive failed attempt monitoring, the environment is vulnerable to efficient brute-force attacks.
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 rate-limiting on login endpoints with progressive delays or account lockout after failed attempts, combined with the password policy fix from CVE-2026-35097 to increase password complexity.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35098 — 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-35098 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