How severe is CVE-2018-13379?

CVE-2018-13379 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2018-13379?

Affected package information for CVE-2018-13379 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2018-13379?

Apply the fortinet fortios security patch or hotfix for CVE-2018-13379 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2018-13379 across my infrastructure?

Inventory every fortinet fortios deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2018-13379 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2018-13379?

O3 detects and blocks CVE-2018-13379 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2018-13379 actively exploited in the wild?

Yes. There are 18 known exploit references for CVE-2018-13379, including 2 documented proof-of-concept exploits on Exploit-DB and 9 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-13379?

CVE-2018-13379 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2018-13379 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-13379 (Fortinet FortiOS SSL VPN Path Traversal Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2018-13379?

CVE-2018-13379 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2018-13379?

CVE-2018-13379 affects fortinet fortios; fortinet fortiproxy (1 version, e.g. 2.0.0). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2018-13379?

A Nuclei detection template exists for CVE-2018-13379, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-13379 published, and has it been updated?

CVE-2018-13379 was published on June 4, 2019 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03 · Ransomware

CVE-2018-13379

CRITICAL

An Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal") in Fortinet FortiOS 6.0.0 to 6.0.4, 5.6.3 to 5.6.7 and 5.4.6 to 5.4.12 and FortiProxy 2.0.0, 1.2.0…

Published

Jun 4, 2019

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

18 known

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

An Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal") in Fortinet FortiOS 6.0.0 to 6.0.4, 5.6.3 to 5.6.7 and 5.4.6 to 5.4.12 and FortiProxy 2.0.0, 1.2.0 to 1.2.8, 1.1.0 to 1.1.6, 1.0.0 to 1.0.7 under SSL VPN web portal allows an unauthenticated attacker to download system files via special crafted HTTP resource requests.

Affected Products

2 products · 5 configurations

fortiosfortinet

≥ 6.0.0 && < 6.0.5

range

Application

fortiproxyfortinet

< 1.2.9

1 version

2.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47287webappshardware

Fortinet FortiOS 5.6.3 - 5.6.7 / FortiOS 6.0.0 - 6.0.4 - Credentials Disclosure (Metasploit)

by Carlos E. Vieira · Aug 19, 2019

Exploit-DB Source

EDB-47288webappshardware

Fortinet FortiOS 5.6.3 - 5.6.7 / FortiOS 6.0.0 - 6.0.4 - Credentials Disclosure

by Carlos E. Vieira · Aug 19, 2019

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every fortinet fortios deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the fortinet fortios security patch or hotfix for CVE-2018-13379 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2018-13379 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2018-13379. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2018-13379 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2018-13379 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works