How severe is CVE-2026-35095?

CVE-2026-35095 has a CVSS 4.0 base score of 4.8, rated medium severity.

Is CVE-2026-35095 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-35095?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-35095 published?

CVE-2026-35095 was published on 2026-06-30.

CVE-2026-35095

CVE-2026-35095 is a medium-severity vulnerability with a CVSS 4.0 base score of 4.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-384.

Key facts

Severity: Medium (CVSS 4.0 base score 4.8)
EPSS exploit prediction: 0% (4th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-384
Published: 2026-06-30
Last modified: 2026-06-30

Description

KTM System e-BOK allows the session identifier to be set by the client prior to authentication. If a cookie with a valid name is set, its value remains unchanged after successful login. This behaviour enables an attacker to fix a session ID for a victim and later hijack the authenticated session. This issue was fixed in the patch published in June 2026.

Frequently asked questions

What is CVE-2026-35095?: KTM System e-BOK allows the session identifier to be set by the client prior to authentication. If a cookie with a valid name is set, its value remains unchanged after successful login. This behaviour enables an attacker to fix a session ID for a victim and later hijack the authenticated session. This issue was fixed in the patch published in June 2026.
How severe is CVE-2026-35095?: CVE-2026-35095 has a CVSS 4.0 base score of 4.8, rated medium severity.
Is CVE-2026-35095 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-35095?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-35095 published?: CVE-2026-35095 was published on 2026-06-30.

References

Other CWE-384 (Session Fixation) vulnerabilities

CVE-2024-11317 — Critical (CVSS 10.0): Session Fixation vulnerabilities allow an attacker to fix a users session identifier before login providing an…
CVE-2024-38513 — Critical (CVSS 10.0): Fiber is an Express-inspired web framework written in Go A vulnerability present in versions prior to 2.52.5 is a…
CVE-2021-20151 — Critical (CVSS 10.0): Trendnet AC2600 TEW-827DRU version 2.08B01 contains a flaw in the session management for the device. The router's…
CVE-2025-67446 — Critical (CVSS 9.8): Improper Authentication (Authentication Bypass) exists in Neterbit NW-431F Router 20241014-IR03 and before. The router…
CVE-2026-25101 — Critical (CVSS 9.8): Bludit allows user's session identifier to be set before authentication. The value of this session ID stays the same…
CVE-2026-24352 — Critical (CVSS 9.8): PluXml CMS allows a user's session identifier to be set before authentication. The value of this session ID stays the…

Browse all CWE-384 (Session Fixation) vulnerabilities →