Skip to content

Vendor

HAVELSAN Inc. vulnerabilities

17 published CVES affecting HAVELSAN Inc., from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
17
Critical
1
High
9
Medium
7
Low
0
Unscored
0
CISA KEV
0
Atom feed of HAVELSAN Inc. alerts

Products

Latest HAVELSAN Inc. CVEs

Newest publication first

  1. HighCVSS 8.1 EPSS 0.32%

    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.

  2. HighCVSS 8.8 EPSS 0.30%

    Improper neutralization of special elements used in an SQL command ('SQL injection') vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows SQL Injection. This issue affects Sef - AI Chatbot Platform: before 2.1. NOTE: The vendor was contacted and it was learned that the...

  3. MediumCVSS 4.9 EPSS 0.27%

    Server-Side request forgery (SSRF) vulnerability in HAVELSAN Inc. Sef - AI Chatbot Platform allows Server Side Request Forgery. This issue affects Sef - AI Chatbot Platform: before 2.1. NOTE: The vendor was contacted and it was learned that the product is not supported.

  4. MediumCVSS 5.3 EPSS 0.26%

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in HAVELSAN Inc. Liman MYS allows Path Traversal. This issue affects Liman MYS: from 2.3.2 before 2.3.4-1124.

  5. HighCVSS 8.8 EPSS 0.52%

    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.

  6. CriticalCVSS 9.4 EPSS 0.46%

    Incorrect Permission Assignment for Critical Resource vulnerability in Havelsan Inc. Dialogue allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects Dialogue: from v1.83 before v1.83.1 or v1.84.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.