Liman MYS EUVD-2026-111851

Exploitation requires a valid low-privilege authenticated session to Liman MYS (PR:L), reachable over the network (AV:N) with low attack complexity and no user interaction. The specific feature, parameter, or endpoint hosting the path-traversal is not described in the available sources. Limiting factors: the attacker must already hold credentials/authenticated access, and impact is confined to confidentiality (arbitrary file read, C:H) with no integrity or availability effect; versions at or above 2.3.5-1132 are not affected.

This is a moderate-severity path traversal (CWE-22) in HAVELSAN's Liman MYS with a CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N). The vector indicates a network-reachable, low-complexity flaw that requires some level of authentication (PR:L) and yields a high confidentiality impact with no integrity or availability impact - consistent with arbitrary file read rather than code execution or data tampering. The vuln.today priority is 'this_month' rather than act_now/emergency, which aligns with the absence of stronger exploitation signals. No EPSS score, no CISA KEV listing, and no POC/exploit reference were supplied, so there is no public exploit identified at time of analysis. The signals are internally consistent (no conflict between CVSS network vector and the advisory): a credentialed attacker can read files outside the intended directory. This is a real but not top-priority issue - it should be patched on a routine cadence, and its practical risk is bounded by the authentication requirement and the read-only (confidentiality-only) impact. Missing data to note: no EPSS, no KEV, no exploit maturity signal, and the single reference is a TR-CERT advisory whose contents are not expanded in the input.

A low-privilege authenticated user of Liman MYS sends a crafted request containing directory-traversal sequences to a parameter that is used to build a file path, causing the application to return files outside the intended directory (e.g., configuration or credential files). The high confidentiality impact (C:H) means sensitive server-side files could be disclosed, though integrity and availability are unaffected. No public exploit code was identified at time of analysis, and the exact vulnerable parameter/endpoint is not described in the available sources.