Fortinet FortiOS/FortiPAM/FortiProxy HTTP Response response splitting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 1.97 |
Summary
A vulnerability labeled as problematic has been found in Fortinet FortiOS, FortiPAM and FortiProxy. Affected is an unknown function of the component HTTP Response Handler. Executing a manipulation can lead to response splitting. This vulnerability appears as CVE-2025-62675. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability classified as problematic was found in Fortinet FortiOS, FortiPAM and FortiProxy (the affected version unknown). This vulnerability affects an unknown part of the component HTTP Response Handler. The manipulation with an unknown input leads to a response splitting vulnerability. The CWE definition for the vulnerability is CWE-113. The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. As an impact it is known to affect integrity. CVE summarizes:
An Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') vulnerability [CWE-113] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.4, FortiOS 7.4 all versions, FortiOS 7.2 all versions, FortiProxy 7.6.0 through 7.6.4, FortiProxy 7.4 all versions, FortiProxy 7.2 all versions may allow an attacker in possession of a valid web filter override token to inject arbitrary headers via tricking a user into clicking on a crafted link.
The advisory is shared for download at fortiguard.fortinet.com. This vulnerability was named CVE-2025-62675 since 10/20/2025. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 07/14/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.fortinet.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.2VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.4
CNA Vector (fortinet): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Response splittingCWE: CWE-113 / CWE-93 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/20/2025 CVE reserved07/14/2026 Advisory disclosed
07/14/2026 VulDB entry created
07/14/2026 VulDB entry last update
Sources
Vendor: fortinet.comAdvisory: FG-IR-26-152
Status: Confirmed
CVE: CVE-2025-62675 (🔒)
GCVE (CVE): GCVE-0-2025-62675
GCVE (VulDB): GCVE-100-378388
Entry
Created: 07/14/2026 19:19Changes: 07/14/2026 19:19 (62)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.