CVE-2026-35097
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 enforces a maximum password length of six numeric digits and does not permit the use of any alphabetic, special, or extended characters. 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 confidenceThe KTM System e-BOK enforces a weak password policy limiting credentials to only six numeric digits (0-9), resulting in a maximum of 1 million possible combinations. This severely reduces password entropy compared to modern complexity requirements, making brute-force and credential stuffing attacks significantly easier to execute.
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.
-
Confirm KTM System e-BOK deploymentIdentify whether your environment contains the KTM System e-BOK application or service. Check installed software listings, service descriptions, or system documentation for this product name.Affected if The system is KTM System e-BOK and is in use
-
Locate password policy configurationAccess the KTM System e-BOK administrative console or configuration files where password policies are defined. Look for settings related to password requirements, character limits, or credential rules.Affected if Password policy settings are accessible and show a 6-digit numeric-only configuration
-
Verify maximum password length settingInspect the password policy to confirm the maximum or required password length is set to 6 characters.Affected if The password length is constrained to 6 characters
-
Check allowed character typesExamine the password policy to determine whether only numeric digits (0-9) are permitted for passwords, excluding letters and special characters.Affected if Only numeric digits are allowed (0-9), no letters or special characters permitted
-
Calculate effective password spaceMultiply the number of allowed characters by itself for the password length. For 6 numeric digits: 10 x 10 x 10 x 10 x 10 x 10 = 1,000,000 combinations.Affected if The effective password space is approximately 1 million or fewer combinations
Your environment is affected if KTM System e-BOK is deployed and its password policy restricts credentials to exactly 6 numeric digits, resulting in approximately 1 million possible combinations.
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 a stronger password policy requiring minimum 8-12 characters with mixed character types (uppercase, lowercase, numbers, special characters), and consider adding multi-factor authentication to compensate for the limited password space.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35097 — 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-35097 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