# CVE-2025-64446: Fortinet FortiWeb Path Traversal

> Attackers can execute administrative commands via crafted HTTP requests due to a relative path traversal flaw in FortiWeb.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 14 Nov 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-hp5v-vp9j-7vp9

## What is CVE-2025-64446?

CVE-2025-64446 is a critical path traversal vulnerability in Fortinet Fortiweb, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A relative path traversal vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.1, FortiWeb 7.6.0 through 7.6.4, FortiWeb 7.4.0 through 7.4.9, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow an attacker to execute administrative commands on the system via crafted HTTP or HTTPS requests.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-64446?

It affects 1 product.


Products: Fortinet Fortiweb.

## How do I fix CVE-2025-64446?

No fix has been published for CVE-2025-64446 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 21 Nov 2025.

## Is CVE-2025-64446 being exploited?

Yes. Attackers have exploited CVE-2025-64446 in the wild since at least 14 Nov 2025.

Public exploit code:

- A scanner for the FortiNet vulnerability CVE-2025-64446 (github_poc): https://github.com/sensepost/CVE-2025-64446
- https://github.com/soltanali0/CVE-2025-64446-Exploit (github_poc): https://github.com/soltanali0/CVE-2025-64446-Exploit
- https://github.com/sxyrxyy/CVE-2025-64446-FortiWeb-CGI-Bypass-PoC (github_poc): https://github.com/sxyrxyy/CVE-2025-64446-FortiWeb-CGI-Bypass-PoC
- PoC de CVE-2025-64446: path traversal a RCE en Fortinet FortiWeb. Solo uso educativo. (github_poc): https://github.com/fevar54/CVE-2025-64446-PoC---FortiWeb-Path-Traversal
- CVE-2025-64446 - A relative path traversal vulnerability in Fortinet FortiWeb 8.0.0 through 8.0.1, FortiWeb 7.6.0 through 7.6.4, FortiWeb 7.4.0 through 7.4.9, FortiWeb 7.2.0 through 7.2.11, FortiWeb 7.0.0 through 7.0.11 may allow an attacker to execute administrative commands on the system via crafted HTTP or HTTPS requests. (github_poc): https://github.com/verylazytech/CVE-2025-64446
- Security research tool for FortiWeb CVE-2025-64446 vulnerability. Automated exploitation framework with advanced logging, real-time metrics, proxy debugging, and professional reporting. Includes retry logic, multi-threading, and configurable settings. For authorized security testing only. CVSS 9.8 Critical. (github_poc): https://github.com/CerberusMrXi/FortiWeb-cve-2025-64446-RCE-exploit

## Other vulnerabilities in Fortinet Fortiweb

- [CVE-2025-25257](https://insights.sbomify.com/CVE-2025-25257/): Fortinet FortiWeb SQL Injection (critical 9.6, exploited in the wild)
- [CVE-2025-58034](https://insights.sbomify.com/CVE-2025-58034/): Fortinet FortiWeb OS Command Injection (medium 6.7, exploited in the wild)
- [CVE-2020-29015](https://insights.sbomify.com/CVE-2020-29015/): SQL injection in Fortinet FortiWeb (critical 9.8)
- [CVE-2020-29016](https://insights.sbomify.com/CVE-2020-29016/): Memory corruption in Fortinet FortiWeb (critical 9.8)
- [CVE-2021-42756](https://insights.sbomify.com/CVE-2021-42756/): Memory corruption in FortiWeb (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64446 and fix it if it is affected.

What it is: CVE-2025-64446 is a critical path traversal vulnerability in Fortinet Fortiweb, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-64446 in the wild since at least 14 Nov 2025.

Affected product: Fortinet Fortiweb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64446/ (Markdown: https://insights.sbomify.com/CVE-2025-64446/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64446
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64446
- OSV: https://osv.dev/vulnerability/CVE-2025-64446

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64446/
Summaries are generated and may contain mistakes; the official description above is the record.