Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Liman MYS password-recovery endpoint
-
DeliveryInitiate forgotten-password flow for target
-
ExploitAbuse weak recovery mechanism
-
ExecutionInduce required user interaction
-
ImpactComplete account takeover (read/modify account data)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Password recovery security
|
| Exploitation Conditions | Exploitation targets the forgotten-password / account-recovery feature of Liman MYS versions 2.3.4-1124 up to (not including) 2.3.5-1131; an attacker must be able to reach that recovery workflow over the network (AV:N) and no attacker authentication is required (PR:N). The key limiting factor is UI:R: the attack requires user interaction to succeed and is not fully autonomous, so it depends on a victim performing some recovery-related action rather than being exploitable purely at the attacker's initiative. The specific mechanism weakness (e.g. token predictability or validation gap) is not described in the available sources. Availability is unaffected (A:N); impact is confined to takeover of the targeted account's data (C:H/I:H). |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1) describes a network-reachable, low-complexity flaw needing no attacker privileges but requiring user interaction (UI:R), with high confidentiality and integrity impact and no availability impact - consistent with an account-takeover via a weak forgotten-password flow (CWE-640). The vuln.today decision label is 'this_week', indicating elevated but non-emergency urgency. No EPSS score, no CISA KEV listing, and no POC/exploit reference are present in the input, so there is no public exploitation signal to corroborate the high base score; the single reference is the TR-CERT (Turkish national CERT / USOM) advisory, which is a credible authoritative source for discovery and patch details but not evidence of in-the-wild use. The practical risk is therefore driven by severity and the fact that it affects an account-recovery mechanism (high value to attackers) rather than by any demonstrated exploitation. The UI:R requirement is a meaningful limiter - the attack is not fully autonomous - and because Liman MYS is a niche, regionally-deployed product, this reads as a genuine but not internet-wide priority: patch within the vendor/CERT-indicated window rather than treat as an active emergency. Note the tag 'Information Disclosure' understates the impact, since the vector also records I:H (integrity), implying account takeover, not merely disclosure. |
| Exploit ScenarioDerived | An unauthenticated attacker abuses weaknesses in the Liman MYS forgotten-password flow (CWE-640) - for example a predictable or improperly validated reset token/flow - to hijack the recovery process and take over a targeted user account, gaining access to its data and the ability to alter it (C:H/I:H). The UI:R metric indicates the attack depends on some user interaction (such as a victim following a reset-related link or action) to complete. No public exploit or POC is identified in the available data, so exploitation would require the attacker to independently reconstruct the flaw from the advisory and patch. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
HAVELSAN Liman MYS releases from 2.3.4-1124 up to but not including 2.3.5-1131 contain a weak forgotten-password recovery mechanism (CWE-640) that lets a network attacker abuse the account-recovery workflow to take over a targeted account, with high confidentiality and integrity impact and no effect on availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1) indicates the flaw is network-reachable and low complexity and needs no attacker credentials, but it is not fully autonomous because a victim must perform some recovery-related action (UI:R); the exact weakness in the recovery flow is not described in the available sources. No CISA KEV entry and no exploit code reference were provided, so no public exploit identified at time of analysis; TR-CERT rates it for remediation within this week.
RemediationAI
Upgrade Liman MYS to 2.3.5-1131 or later, the first release outside the stated vulnerable range (affected: 2.3.4-1124 before 2.3.5-1131), and verify the deployed build number after upgrading; the TR-CERT advisory at https://siberguvenlik.gov.tr/guvenlik-bildirimleri/detay/tr-26-1396 should be reviewed for any installation-specific guidance. Because the flaw sits in the forgotten-password recovery workflow, confirm after upgrading that reset requests for test accounts behave as expected. The available sources do not describe any workaround or compensating control for this issue, so no feature-disable or access-restriction mitigation can be recommended from the supplied data; treat applying the fixed build as the complete remediation path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-640, Weak Password Recovery Mechanism for Forgotten Password, meaning the account-recovery path does not bind a recovery secret tightly enough to the legitimate account owner before a password reset is accepted. The affected component is the forgotten-password / account-recovery feature in HAVELSAN Liman MYS, identified by the CPE pattern cpe:2.3:a:havelsan_inc.:liman_mys:*:*:*:*:*:*:*:* (a wildcarded version match), with the affected range pinned by the advisory to 2.3.4-1124 through 2.3.5-1131. The assessed vector shows the recovery workflow is reachable over the network (AV:N) at low attack complexity (AC:L) and without any attacker authentication (PR:N), while the UI:R metric records that a user-interaction step is part of the exploit path, so success depends on a victim engaging with the recovery process rather than on attacker-initiated requests alone. Scope is unchanged (S:U) and availability is unaffected (A:N); the demonstrated impact is full compromise of the targeted account's confidentiality and integrity (C:H/I:H). The sources do not state which concrete mechanism is deficient - for example predictable recovery tokens, missing validation of recovery identifiers, or an unbound reset step - so the precise trigger is not described in the available sources.
Know when Liman Mys gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Network-reachable recovery flow with no attacker auth (AV:N/PR:N/AC:L) but needing victim interaction (UI:R); account takeover yields C:H/I:H, no availability impact.
Primary rating from Vendor (TR-CERT).
CVSS VectorVendor: TR-CERT
Lifecycle Timeline
2DescriptionCVE.org
Weak Password Recovery Mechanism for Forgotten Password vulnerability in HAVELSAN Inc. Liman MYS allows Password Recovery Exploitation.
This issue affects Liman MYS: from 2.3.4-1124 before 2.3.5-1131.
Executive ViewAI
HAVELSAN Liman MYS, a critical IT management platform, has a high-severity flaw in its password recovery mechanism that allows unauthorized account takeover. This puts sensitive data and system integrity at risk across the organization, and while no exploitation has been observed, the potential impact warrants immediate leadership attention.
Disable the forgotten-password recovery functionality or restrict access to it from trusted networks only; enforce multifactor authentication for all accounts; monitor account recovery events for anomalies.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Missing authorization controls in HAVELSAN Liman MYS (versions 2.2.3 through before 2.3.1) allow a low-privileged authen
Privilege escalation in Liman MYS (HAVELSAN Inc.) versions 2.2.3 through pre-2.3.1 enables authenticated low-privilege u
Privilege escalation and unauthorized functionality access in HAVELSAN Liman MYS (Yönetim Sistemi) before release.Master
Path traversal in HAVELSAN Liman MYS before 2.3.5-1132 allows an authenticated low-privilege user to read files outside
A path traversal flaw (CWE-22) in HAVELSAN Liman MYS versions 2.3.2 up to but not including 2.3.4-1124 allows remote, un
EUVD-2026-109777
GHSA-qh9j-c6pq-98xh
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB