CVE.org (no NVD analysis yet)· CNA TR-CERT

CVE-2026-105457: Authenticated Arbitrary Local File Read via Path Traversal in HAVELSAN's Liman MYS

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: HAVELSAN Inc. Liman MYS 2.3.5-1132.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to HAVELSAN Inc. Liman MYS 2.3.5-1132 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in HAVELSAN Inc. Liman MYS allows Path Traversal. This issue affects Liman MYS: before 2.3.5-1132.

MediumCVSS 6.5 · v3.1—No exploit Fix available

Path traversal

EUVD-2026-111851

Published: Oct 28, 2026
Updated: Nov 5, 2026
EPSS: 0.4% · 37th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · TR-CERT: 6.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (TR-CERT). Independent of NVD's CPE analysis and usually ahead of it.

HAVELSAN Inc. Liman MYS
- before 2.3.5-1132affected · semver

Same product

havelsan inc.: all records

Other highest-scoring records for the same primary product.

CVE-2026-18650Missing Authorization Leading to Root Code Execution in HAVELSAN's Liman MYS
35Monitor
CVE-2026-17070Vault Credential Confusion via Authorization Bypass in HAVELSAN's Liman MYS
35Monitor
CVE-2026-13696LDAP Injection in HAVELSAN's Liman MYS
35Monitor

Published before and after this one in the same product

← EarlierCVE-2026-11348Jul 7, 2026 · Authentication Bypass in HAVELSAN's Open Source Project Liman MYS
32Monitor
← EarlierCVE-2026-19532Sep 24, 2026 · Path Traversal in HAVELSAN's Liman MYS
21Monitor
← EarlierCVE-2026-94380Oct 26, 2026 · Host Header Injection in HAVELSAN's Liman MYS
32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
HAVELSAN Inc. Liman MYS	2.3.5-1132	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedOct 28, 2026
Fix recordedOct 28, 2026same day
TodayNov 11, 2026+14 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Selahattin Dumanfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-1953234 days apartPath Traversal in HAVELSAN's Liman MYS
21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-11348113 days apartAuthentication Bypass in HAVELSAN's Open Source Project Liman MYS
32Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-1421 · Oct 28, 2026(HAVELSAN - Liman MYS Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

SSVC exploitation— → noneNov 5, 2026, 7:07 PM UTC
Exploit maturity— → noneOct 28, 2026, 11:07 AM UTC
Fix✗ → ✓Oct 28, 2026, 11:07 AM UTC

For records you follow, these changes also arrive as notifications. →

References

siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1421

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records