CVE-2026-11340
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing Authorization vulnerability in HAVELSAN Inc. Liman MYS allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Liman MYS: before release.Master.1107.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing Authorization vulnerability in HAVELSAN Liman MYS allows unauthenticated or unauthorized users to access certain functionality that should be restricted by Access Control Lists (ACLs). This affects versions before release.Master.1107.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Liman MYS versionAccess the Liman MYS administrative interface and navigate to System Settings > About, or check the installation directory for version files. Alternatively, query the web interface for version information if available.Affected if The installed version is earlier than release.Master.1107 (e.g., release.Master.1106, release.Master.1050, or any pre-release version)
-
Confirm web interface accessibilityDetermine if the Liman MYS web portal is externally accessible or accessible to unauthorized users by checking the network configuration and web server bindings.Affected if The web interface is reachable without authentication or by users outside the intended ACL scope
-
Review ACL configuration filesInspect the Liman MYS configuration directory for ACL definition files, permission sets, or access control policies. Look for files controlling user role assignments and endpoint access permissions.Affected if ACL files exist but contain overly permissive rules, missing role restrictions, or permit unauthenticated access to protected endpoints
-
Verify authorization enforcement on sensitive endpointsTest access to administrative functions, user management modules, or system configuration areas from an unauthenticated or low-privilege account context.Affected if Sensitive functionality is accessible without proper authorization credentials or role validation
The environment is affected if Liman MYS version is before release.Master.1107 and the web interface or specific modules are accessible to unauthorized users due to missing ACL enforcement.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Liman MYS release.Master.1107 or later which contains proper authorization constraints for the affected functionality.
release.Master.1107
- Upgrade HAVELSAN Liman MYS to release.Master.1107 or later to resolve the missing authorization vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11340 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data