dbcve.org
Improper Signature VerificationWeakness · CWE-347

CVE-2026-11348

HIGH · 8.1 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 →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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 verification of cryptographic signature vulnerability in HAVELSAN Inc. Liman MYS allows Fake the Source of Data. 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 confidence

Improper cryptographic signature verification in HAVELSAN Liman MYS allows attackers to spoof the source of data by presenting falsified signed data. The vulnerability exists in the signature validation logic before release.Master.1107, enabling authentication bypass where malicious data appears to originate from a trusted source.

MitigationUpgrade Liman MYS to release.Master.1107 or later which contains the cryptographic signature verification fix. Verify that signature validation correctly rejects improperly signed data from untrusted sources.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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 installed Liman MYS version
    Locate the Liman MYS installation directory and check for version information files, typically found in /opt/liman or the application's base directory. Look for version manifest files, about pages within the web interface, or run 'liman --version' if the CLI is available.
    Affected if The installed version is release.Master.1106 or earlier (any version before release.Master.1107)
  2. Locate signature validation configuration
    Search for configuration files related to signature verification, typically in /etc/liman, the config/ directory, or within the web application's settings. Look for files named signature.conf, verification.yml, or similar containing 'signature', 'verify', or 'cryptographic' keywords.
    Affected if Signature validation is enabled in the configuration (the vulnerability only applies when this feature is active)
  3. Check signature validation module status
    Examine the Liman MYS administrative interface or check the running services for modules related to data signing or signature verification. Look for entries in the plugin/module list that handle signed data or cryptographic validation.
    Affected if The signature validation module is loaded or enabled in the running system
  4. Review signature validation logs
    Check application logs in /var/log/liman or similar directories for entries containing 'signature', 'verification failed', 'invalid signature', or 'authentication bypass'. These logs may indicate whether the flawed validation logic has been exercised.
    Affected if Logs show signature validation is actively processing signed data requests
  5. Verify signature validation behavior with test data
    If possible, attempt to submit a request with falsified signed data to an endpoint that uses signature validation. Observe whether the application accepts or rejects improperly signed data from an untrusted source.
    Affected if The application accepts falsified signed data that should be rejected (indicates the vulnerability is present)

A user is affected if their Liman MYS installation is release.Master.1106 or earlier AND the signature validation feature is enabled and actively processing signed data.

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 Liman MYS to release.Master.1107 or later which contains the cryptographic signature verification fix. Verify that signature validation correctly rejects improperly signed data from untrusted sources.

Recommended fix Moderate confidence

release.Master.1107 or later

  1. 1. Backup the current Liman MYS installation and database before proceeding with any upgrade
  2. 2. Download the latest Liman MYS release (release.Master.1107 or later) from the official HAVELSAN repository or distribution channel
  3. 3. Review the upgrade documentation provided with release.Master.1107 for any specific migration requirements
  4. 4. Stop the Liman MYS services
  5. 5. Install the new release.Master.1107 package
  6. 6. Verify the integrity of downloaded packages using official checksums/signatures provided by HAVELSAN
  7. 7. Start the Liman MYS services after installation
  8. 8. Verify that Liman MYS is functioning correctly and that the signature verification is working properly
Caveat Review release notes for release.Master.1107 to check for any breaking changes or required configuration updates before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11348 — 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-11348 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