{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-105457 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-105457 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-105457 is a medium-severity vulnerability in HAVELSAN Inc. Liman MYS, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-105457 and fix it if it is affected.\n\nWhat it is: CVE-2026-105457 is a medium-severity vulnerability in HAVELSAN Inc. Liman MYS, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-105457 in the wild and no public exploit code.\n\nAffected product: HAVELSAN Inc. Liman MYS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-105457/ (Markdown: https://insights.sbomify.com/CVE-2026-105457/index.md)","id":"CVE-2026-105457","markdown":"https://insights.sbomify.com/CVE-2026-105457/index.md","name":"CVE-2026-105457","record":{"aliases":["GHSA-v4rx-xwqp-8v54"],"analysis":null,"analysis_generated_by":null,"assigner":"TR-CERT","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in HAVELSAN Inc. Liman MYS allows Path Traversal.\n\nThis issue affects Liman MYS: before 2.3.5-1132.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Authenticated Arbitrary Local File Read via Path Traversal in HAVELSAN's Liman MYS","id":"CVE-2026-105457","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Reliance on Untrusted Inputs in a Security Decision in GitLab","id":"CVE-2026-105458"},"packages":[],"prev":{"headline":"IBM Sterling Connect:Direct for Unix Improper Privilege Management","id":"CVE-2026-105453"},"products":["Liman MYS"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["HAVELSAN Inc."]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-105457/"}