CVE-2025-25255
published 2025-10-14CVE-2025-25255: An Improperly Implemented Security Check for Standard vulnerability [CWE-358] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiProxy 7.6.0 through…
PriorityP425medium4.3CVSS 3.1
AVNACLPRLUINSUCNILAN
EPSS
0.43%
34.4th percentile
An Improperly Implemented Security Check for Standard vulnerability [CWE-358] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiProxy 7.6.0 through 7.6.3, FortiProxy 7.4.0 through 7.4.11, FortiProxy 7.2 all versions, FortiProxy 7.0.1 through 7.0.22 may allow an unauthenticated proxy user to bypass the domain fronting protection feature via crafted HTTP requests.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| fortinet | fortinet | — | — |
| fortinet | fortios | — | — |
| fortinet | fortios | >= 7.6.0 < 7.6.4 | 7.6.4 |
| fortinet | fortios | 7.6.0 – 7.6.3 | — |
| fortinet | fortiproxy | — | — |
| fortinet | fortiproxy | >= 7.0.1 < 7.6.4 | 7.6.4 |
| fortinet | fortiproxy | 7.0.1 – 7.0.22 | — |
| fortinet | fortiproxy | 7.2.0 – 7.2.15 | — |
| fortinet | fortiproxy | 7.4.0 – 7.4.11 | — |
| fortinet | fortiproxy | 7.6.0 – 7.6.3 | — |
| msrc | cbl2_qt5-qtbase_5.12.11-14_on_cbl_mariner_2.0 | — | — |
| msrc | cbl2_qt5-qtbase_5.12.11-15_on_cbl_mariner_2.0 | — | — |
| msrc | cbl_mariner_2.0_arm | — | — |
| msrc | cbl_mariner_2.0_x64 | — | — |
CVSS provenance
nvdv3.14.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
vendor_msrc7.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-mgv9-8jj6-qq93: An Improperly Implemented Security Check for Standard vulnerability [CWE-358] in FortiProxy 7
ghsa_unreviewed·2025-10-14
CVE-2025-25255 [MEDIUM] CWE-358 GHSA-mgv9-8jj6-qq93: An Improperly Implemented Security Check for Standard vulnerability [CWE-358] in FortiProxy 7
An Improperly Implemented Security Check for Standard vulnerability [CWE-358] in FortiProxy 7.6.0 through 7.6.3, 7.4 all versions, 7.2 all versions, 7.0.1 through 7.0.21, and FortiOS 7.6.0 through 7.6.3 explicit web proxy may allow an authenticated proxy user to bypass the domain fronting protection feature via crafted HTTP requests.
Fortinet
Domain fronting protection bypass in explicit web proxy
vendor_fortinet·2025-10-14·CVSS 5.3
CVE-2025-25255 [MEDIUM] CWE-358 Domain fronting protection bypass in explicit web proxy
FG-IR-24-372: Domain fronting protection bypass in explicit web proxy
An Improperly Implemented Security Check for Standard vulnerability [CWE-358] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiProxy 7.6.0 through 7.6.3, FortiProxy 7.4.0 through 7.4.11, FortiProxy 7.2 all versions, FortiProxy 7.0.1 through 7.0.22 may allow an unauthenticated proxy user to bypass the domain fronting protection feature via crafted HTTP requests.
CVEs: CVE-2025-25255
CWEs: CWE-358
CVSS: 5.3 (medium)
Affected products: FortiOS, FortiProxy, Fortinet
Microsoft
In Qt 5.9.x through 5.15.x before 5.15.9 and 6.x before 6.2.4 on Linux and UNIX QProcess could execute a binary from the current working directory when not found in the PATH.
vendor_msrc·2022-02-08·CVSS 7.8
CVE-2022-25255 [HIGH] In Qt 5.9.x through 5.15.x before 5.15.9 and 6.x before 6.2.4 on Linux and UNIX QProcess could execute a binary from the current working directory when not found in the PATH.
In Qt 5.9.x through 5.15.x before 5.15.9 and 6.x before 6.2.4 on Linux and UNIX QProcess could execute a binary from the current working directory when not found in the PATH.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mar
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-10-14
Published