CVE-2026-35098
Deferred Deferred - Pending Action

Brute-Force Vulnerability in KTM System e-BOK

Vulnerability report for CVE-2026-35098, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-06-30

Last updated on: 2026-06-30

Assigner: CERT.PL

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-30
Last Modified
2026-06-30
Generated
2026-07-20
AI Q&A
2026-06-30
EPSS Evaluated
2026-07-19
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
ktm system_e-bok to 2026-06-01 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-307 The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability in KTM System e-BOK is due to the absence of any limit or timeout on consecutive login attempts. This means an attacker can make unlimited authentication requests without restriction.

Because there is no rate-limiting, attackers can efficiently perform brute-force attacks to guess user passwords.

This vulnerability becomes especially critical when combined with CVE-2026-35097, where passwords are limited to a six-digit numeric format, making brute-force attacks feasible in a short time.

Detection Guidance

The vulnerability in KTM System e-BOK allows unlimited consecutive login attempts without any rate limiting or timeout. To detect this vulnerability on your system or network, you can monitor authentication logs for repeated failed login attempts from the same IP address or user account in a short period of time.

Commands to help detect such behavior might include searching authentication logs for repeated failures. For example, on a Linux system, you could use:

  • grep 'failed login' /var/log/auth.log | awk '{print $1,$2,$3,$11}' | sort | uniq -c | sort -nr
  • or to detect rapid repeated login attempts from the same IP:
  • grep 'failed login' /var/log/auth.log | awk '{print $11}' | sort | uniq -c | sort -nr

Additionally, network monitoring tools can be configured to alert on high volumes of authentication requests to the e-BOK login endpoint, which may indicate brute-force attempts exploiting the lack of rate limiting.

Impact Analysis

This vulnerability allows attackers to repeatedly attempt to guess user passwords without any restriction, increasing the risk of unauthorized access to user accounts.

If an attacker successfully brute-forces a password, they can gain access to sensitive information or perform unauthorized actions within the system.

The impact is heightened by the fact that passwords are limited to a six-digit numeric format, making it easier and faster for attackers to compromise accounts.

Compliance Impact

The vulnerability in KTM System e-BOK allows unlimited authentication attempts due to the lack of rate-limiting, enabling efficient brute-force attacks on user accounts. This can lead to unauthorized access to personal and financial information of tenants or cooperative members.

Such unauthorized access risks violating data protection regulations like GDPR, which require appropriate security measures to protect personal data from unauthorized access and breaches.

Additionally, the weak password policy (six-digit numeric passwords) combined with this vulnerability increases the risk of compromise, further impacting compliance with standards that mandate strong authentication controls.

Mitigation Strategies

To mitigate this vulnerability, apply the patch published in June 2026 that fixes the issue by implementing limits or timeouts on consecutive login attempts.

Additionally, consider enforcing stronger password policies beyond the six-digit numeric format to reduce the risk of brute-force attacks.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-35098. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart