dbcve.org
CWE-90Weakness · CWE-90

CVE-2026-13696

HIGH · 8.8 CVSS v3.1 Published 2026-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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 · unedited
Improper neutralization of special elements used in an LDAP query ('LDAP injection') vulnerability in HAVELSAN Inc. Liman MYS allows LDAP Injection. 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 · high confidence

LDAP injection vulnerability in HAVELSAN Liman MYS allows attackers to manipulate LDAP queries through unsanitized user input. The vulnerability exists in versions before release.Master.1107, where special characters in user-supplied data are not properly escaped before being incorporated into LDAP directory searches.

MitigationUpgrade to Liman MYS release.Master.1107 or later. If immediate patching is not possible, implement input validation and proper LDAP escaping (using backslash encoding for special characters like * ( ) \ NUL) on all user-supplied parameters before constructing LDAP queries.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Liman MYS installation and version
    Locate the Liman MYS installation directory and check for version information files. Common locations include /opt/liman or /var/www/liman. Look for a version file, changelog, or the main application file that displays the version.
    Affected if The installed version is release.Master.1106 or earlier, or the version cannot be determined but is known to be from before release.Master.1107
  2. Verify LDAP authentication is configured
    Check the Liman MYS configuration files for LDAP/Active Directory integration settings. Look for LDAP connection parameters, user authentication sources, or directory service configurations in config files.
    Affected if LDAP authentication or directory integration is enabled and the Liman MYS version is before release.Master.1107
  3. Identify user input fields that interact with LDAP queries
    Review web application source code or configuration files for parameters that accept user input and are used in LDAP search queries. Look for query construction patterns involving user-supplied data.
    Affected if User-supplied parameters are directly used in LDAP search filters without apparent sanitization, and the version is before release.Master.1107
  4. Inspect LDAP query handling for special characters
    Examine the LDAP query builder or search function implementations in the Liman MYS code. Check if special characters (* ( ) \ NUL) are escaped or validated before being included in LDAP filters.
    Affected if LDAP queries incorporate user input without proper escaping of special characters, and the version is before release.Master.1107

A user is affected if HAVELSAN Liman MYS is installed with LDAP integration enabled and the version is release.Master.1106 or earlier.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Liman MYS release.Master.1107 or later. If immediate patching is not possible, implement input validation and proper LDAP escaping (using backslash encoding for special characters like * ( ) \ NUL) on all user-supplied parameters before constructing LDAP queries.

Recommended fix Moderate confidence

release.Master.1107

  1. 1. Backup the current Liman MYS installation and database.
  2. 2. Review the release notes for Master.1107 to understand any prerequisites or migration requirements.
  3. 3. Download Liman MYS release Master.1107 from the official HAVELSAN/Liman repository or vendor distribution channel.
  4. 4. Stop the Liman MYS service before applying the update.
  5. 5. Apply the update/upgrade following the vendor's standard upgrade procedure for Liman MYS.
  6. 6. Verify the upgrade was successful by checking the version number.
  7. 7. Test LDAP authentication functionality to confirm the LDAP injection vulnerability is remediated.
  8. 8. Restart the Liman MYS service.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13696 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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