Skip to main content
Mallory
MediumExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2019-5591: LDAP Server Impersonation in Fortinet FortiOS

Published Aug 14, 2020 · Updated 1 day ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS6.5Medium · v3.1
EPSS18.6%97th percentile
CISA KEVYesAdded Nov 3, 2021
In the wildActivePer CISA KEV
Vendor
Fortinet
IdentifiersCVE-2019-5591CWE-295

CVE-2019-5591 is a default-configuration vulnerability in Fortinet FortiOS involving improper LDAP server certificate validation. An unauthenticated attacker on the same subnet can impersonate the LDAP server and intercept sensitive information, including authentication credentials. Affected releases include FortiOS 5.4.6–5.4.12, 5.6.3–5.6.7, 6.0.0–6.0.3, and 6.2.0.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality of LDAP authentication exchanges and can expose authentication credentials. Captured credentials may facilitate subsequent unauthorized access, depending on their privileges and other access controls. The vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog with known ransomware campaign use; ransomware execution and broader network compromise are follow-on outcomes rather than direct capabilities of this flaw.

Mitigation

If you can’t patch tonight, do this now.

Use network segmentation and access controls to prevent untrusted systems from sharing the subnet used for FortiOS LDAP communications, and restrict LDAP connectivity to authorized infrastructure. These measures reduce opportunities for same-subnet impersonation but do not replace patching. If exploitation is suspected, investigate authentication activity and rotate potentially exposed credentials.

Remediation

Patch, then assume compromise.

Apply Fortinet updates addressing CVE-2019-5591 in accordance with advisory FG-IR-19-037. Upgrade affected appliances to a supported, patched FortiOS release. Exact minimum fixed versions are not established by the available information.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FortinetFortiosoperating_system
FAQ

Frequently asked questions

Is CVE-2019-5591 exploited in the wild?
Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
Is there a public exploit for CVE-2019-5591?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2019-5591, the earliest disclosed Oct 16, 2025.
Is there a patch for CVE-2019-5591?
Apply Fortinet updates addressing CVE-2019-5591 in accordance with advisory FG-IR-19-037. Upgrade affected appliances to a supported, patched FortiOS release.
What products are affected by CVE-2019-5591?
Fortinet Fortios.
How severe is CVE-2019-5591?
CVE-2019-5591 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 18.6% (97th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+12 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence2Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.