# CVE-2026-35097: Weak Password Requirements in KTM System e-BOK

> Weak password policy in KTM System e-BOK allows attackers to easily guess credentials and take over user accounts.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-fv8h-9jrm-xcpc

## What is CVE-2026-35097?

CVE-2026-35097 is a medium-severity vulnerability in KTM System e-BOK, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KTM 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.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2026-35097?


## How do I fix CVE-2026-35097?

No fix has been published for CVE-2026-35097 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35097 being exploited?

There is no known exploitation of CVE-2026-35097 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35097 and fix it if it is affected.

What it is: CVE-2026-35097 is a medium-severity vulnerability in KTM System e-BOK, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35097 in the wild and no public exploit code.

Affected product: KTM System e-BOK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35097/ (Markdown: https://insights.sbomify.com/CVE-2026-35097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35097
- OSV: https://osv.dev/vulnerability/CVE-2026-35097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35097/
Summaries are generated and may contain mistakes; the official description above is the record.